Bazzite is a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
bazzite-local-build-problem on git main took 6m23s x ./build-and-switch-bazzite.sh
+ sudo buildah build -t localhost/bazzite-gnome:local -f Containerfile.bazzite .
STEP 1/2: FROM ghcr.io/ublue-os/bazzite-gnome:stable
STEP 2/2: RUN rpm-ostree install hardinfo2 && ostree container commit
<Cut>
+ sudo bootc switch --transport containers-storage localhost/bazzite-gnome:local
ERROR Switching: Pulling: Preparing import: Fetching manifest: Parsing manifest layout: Missing ostree.final-diffid sha256:12787d84fa137cd5649a9005efe98ec9d05ea46245fdc50aecb7dd007f2035b1
However, if I build off of the ghcr.io/ublue-os/silverblue-main:41, this error does not occur.
What did you expect to happen?
I expect to be able to sudo buildah build or sudo podman build and then bootc switch to the image. Something about how the bazzite image is built is breaking my ability to build off of the image.
I've tried pushing the image up to a registry (ghcr.io/dkolb/bazzite-gnome) and it still has issues.
I'm a bit at the end of my rope here, because I just cannot figure out what exactly what about the Bazzite image makes this process break.
Output of rpm-ostree status
bazzite-local-build-problem on git main > rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:0663cb3c11263222062040a8d3c9dcdac991980ce63a38de170b9bcbdd08a44f
Version: 41.20241112.1 (2024-11-12T23:54:35Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:0663cb3c11263222062040a8d3c9dcdac991980ce63a38de170b9bcbdd08a44f
Version: 41.20241112.1 (2024-11-12T23:54:35Z)
LocalPackages: bluetooth-suspend-fix-0.0.0-0.git.1.0c588cf.fc40.x86_64
Hardware
bazzite-local-build-problem on git main > cat /sys/devices/virtual/dmi/id/product_name
AMD Ryzen 9 7950X3D 16-Core Processor
Extra information or context
I've been wandering most of the Universal Build/Blue Build ecosystem it seems trying to solve this, lol.
Describe the bug
See demo repo with scripts showing steps taken to reproduce: https://github.com/dkolb/bazzite-local-build-problem
However, if I build off of the
ghcr.io/ublue-os/silverblue-main:41
, this error does not occur.What did you expect to happen?
I expect to be able to
sudo buildah build
orsudo podman build
and thenbootc switch
to the image. Something about how the bazzite image is built is breaking my ability to build off of the image.I've tried pushing the image up to a registry (
ghcr.io/dkolb/bazzite-gnome
) and it still has issues.I'm a bit at the end of my rope here, because I just cannot figure out what exactly what about the Bazzite image makes this process break.
Output of
rpm-ostree status
Hardware
Extra information or context
I've been wandering most of the Universal Build/Blue Build ecosystem it seems trying to solve this, lol.