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

rpm-ostree upgrade

for some reason is trying to pull from main bazzite again, so I did a rebase again.

Now,

rpm-ostree upgrade

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?

FengLengshunOP•9/27/23, 2:49 AM

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

rpm-ostree upgrade

outputs. It's the main bazzite image again.

EyeCantCU•9/27/23, 3:09 AM

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

ARG IMAGE_NAME="${IMAGE_NAME}"
ARG IMAGE_VENDOR="ublue-os"
ARG BASE_IMAGE_NAME="${BASE_IMAGE_NAME}"
ARG IMAGE_FLAVOR="${IMAGE_FLAVOR}"
ARG FEDORA_MAJOR_VERSION="${FEDORA_MAJOR_VERSION}"

ARG IMAGE_NAME="${IMAGE_NAME}"
ARG IMAGE_VENDOR="ublue-os"
ARG BASE_IMAGE_NAME="${BASE_IMAGE_NAME}"
ARG IMAGE_FLAVOR="${IMAGE_FLAVOR}"
ARG FEDORA_MAJOR_VERSION="${FEDORA_MAJOR_VERSION}"

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...

EEyeCantCU You need this script in your repo and to run it in your containerfile https://g...

FengLengshunOP•9/29/23, 3:03 AM

where do I put the image-info.sh?

./script/post

./script/post

FengLengshunOP•9/29/23, 3:03 AM

And does this work?

Containerfile.txt1.43KB

EyeCantCU•9/29/23, 3:20 AM

I'll take a looksee

EyeCantCU•9/29/23, 3:24 AM

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

FengLengshunOP•9/29/23, 3:56 AM

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)

Containerfile.txt1.59KB

FengLengshunOP•9/29/23, 10:51 AM

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

Containerfile.txt1.59KB

image-info.sh.txt588B

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.