From 5d03a90531dbcb2c8ccbaca60379d3f0d2804911 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Tue, 18 Nov 2025 14:25:52 -0500 Subject: [PATCH] osbuild: pause using container-storage for builds Using container storage in the supermin VM was first introduced in 9190a34. This was a nice optimization but it's causing issues where the digest of the deployed container within the bootimages is different than what is in our metadata and what is pushed to the registry. See https://github.com/coreos/fedora-coreos-tracker/issues/2066 for more information. --- src/runvm-osbuild | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/runvm-osbuild b/src/runvm-osbuild index 5193db3eb3..2688248d8e 100755 --- a/src/runvm-osbuild +++ b/src/runvm-osbuild @@ -76,9 +76,14 @@ extra_kargs=$(getconfig "extra-kargs-string" "") # if it exists then let's check here to see if the container exists # in local container storage. If it does then we'll just pass that # and not pass any ociarchive info into the build. -if podman image exists "${container_repo}:${container_tag}"; then - ostree_container="" -fi +# +# XXX: Disabling this for now as it ends up with inconsistent digests +# in our deployed bootimages versus what's pushed to the registry +# and is causing zincati to not work. +# https://github.com/coreos/fedora-coreos-tracker/issues/2066 +#if podman image exists "${container_repo}:${container_tag}"; then +# ostree_container="" +#fi # Since it doesn't exist create loop-control [ ! -e /dev/loop-control ] && mknod /dev/loop-control c 10 237