rpm-ostree upgrade sometimes pulls from bazzite repo instead of my selected repo
Is there some sort of hardcoding in the auto-updater? I noticed this because randomly my virt-manager and stuff just disappeared, and when I checked it I was actually on the main bazzite image instead of my personal one.
So I just did a rebase to my personal image two days ago to fix it, and this morning decided to do a manual update (screenshot attached) before starting my work.
rpm-ostree upgrade
for some reason is trying to pull from main bazzite again, so I did a rebase again.
Now, rpm-ostree upgrade
correctly pulls from my personal image, so my first thought is that maybe the bazzite url is hardcoded in a schedule service like the auto-updater or something?10 Replies
Yeah, I think it might be the auto-updater, I got an auto-update notification, so I checked the pending transaction and what
rpm-ostree upgrade
outputs. It's the main bazzite image again.You need this script in your repo and to run it in your containerfile
https://github.com/ublue-os/bazzite/blob/main/system_files/shared/tmp/image-info.sh
You'll also need this in your Containerfile after the FROM statement
Replace IMAGE_VENDOR with your GitHub username
GitHub
bazzite/system_files/shared/tmp/image-info.sh at main · ublue-os/ba...
Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other h...
where do I put the image-info.sh?
./script/post
?And does this work?
I'll take a looksee
You could place it at the root and copy it like this:
COPY image-info.sh /tmp
And then at the bottom just put
/tmp/image-info.sh && \
Right after /tmp/build.sh && \
Otherwise it looks great. I'd probably move scripts and usr and everything into a shared directory so that you can just do
COPY system_files/shared /
In one go but that's up to you
alright, pushing this to gh now, we'll tell if works (I also have a Kinoite image build as a backup of sort in the same repo, so hopefully there's no issue there)
I got an error about unbound variable. Not sure what I'm doing wrong - I didn't set it in image-info.sh at first, then I set it but they both resulted the same?
https://github.com/bayazidbh/ublue-whitesur/actions/runs/6347031084/job/17241420087#step:9:859
GitHub
add image-vendor var to image-info.sh · bayazidbh/ublue-whitesur@42...
Contribute to bayazidbh/ublue-whitesur development by creating an account on GitHub.
All of this needs to go after FROM
https://github.com/bayazidbh/ublue-whitesur/blob/42e14b61ccb6d5c0cbfe81c171f5601c5cc8f034/Containerfile#L4
GitHub
ublue-whitesur/Containerfile at 42e14b61ccb6d5c0cbfe81c171f5601c5cc...
Contribute to bayazidbh/ublue-whitesur development by creating an account on GitHub.
Thanks, that builds correctly, seems that
rpm-ostree upgrade
pulls correctly now, will tell if there's any issue, again thanks mate!Happy to help and happy to know that. Glad you got it working!