bootc update --check failed

[djarbz]

I'm just getting started with bootc.
Generated an auto-install iso via osbuild.
Deployed it to a QEMU vm, updated the registry image and cannot pull updates.
I did login to the registry for /etc/ostree/auth.json
I also created /run/install but then it asks for /run/install/repo.
I figure something is wrong that just creating the directories isn't the proper fix.

bootc update --check
ERROR Upgrading: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: lstat /run/install: no such file or directory

[djarbz]

Possibly of interest...

bootc status
● Booted image: oci:/run/install/repo/container
        Digest: sha256:ad0bfbba95114326ef9b8e59e7ed4cc0e6422cbb11c74e3e21cd4cd3efa32499
       Version: 42.20250423.0 (2025-04-24 04:49:30.030543614 UTC)

But that path doesn't exist...

ls -l /run
total 24
drwxr-xr-x.  6 root   root    160 Apr 24 17:49 NetworkManager
-rw-------.  1 root   root      0 Apr 24 17:49 agetty.reload
drwxr-xr-x.  2 avahi  avahi    80 Apr 24 17:49 avahi-daemon
drwxr-xr-x.  2 root   root     80 Apr 24 17:49 blkid
drwxr-x---.  2 chrony chrony   80 Apr 24 17:49 chrony
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 chrony-dhcp
drwxr-xr-x.  4 root   root    360 Apr 24 17:49 cloud-init
drwxr-xr-x.  2 root   root    100 Apr 24 17:49 cockpit
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 console
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 console-login-helper-messages
drwx------.  4 root   root     80 Apr 24 17:49 containers
drwxr-xr-x.  6 root   root    120 Apr 24 17:49 credentials
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 criu
drwx------.  2 root   root     40 Apr 24 17:49 cryptsetup
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 dbus
drwxr-xr-x.  2 root   root    100 Apr 24 17:49 dhcpcd
prw-------.  1 root   root      0 Apr 24 17:49 dmeventd-client
prw-------.  1 root   root      0 Apr 24 17:49 dmeventd-server
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 faillock
srw-rw-rw-.  1 root   root      0 Apr 24 17:49 gssproxy.default.sock
-rw-------.  1 root   root      5 Apr 24 17:49 gssproxy.pid
srw-rw-rw-.  1 root   root      0 Apr 24 17:49 gssproxy.sock
lrwxrwxrwx.  1 root   root      3 Apr 24 17:49 host -> ../
prw-------.  1 root   root      0 Apr 24 17:49 initctl
drwxr-xr-x   3 root   root     60 Apr 24 17:49 initramfs
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 irqbalance
drwxr-x--x.  4 root   root    120 Apr 24 17:49 libpod
drwxr-xr-x.  5 root   root    120 Apr 24 17:49 lock
drwxr-xr-x.  3 root   root     60 Apr 24 17:49 log
drwx------.  2 root   root     80 Apr 24 17:49 lvm
drwx--x---.  2 root   root     40 Apr 24 17:49 mdadm
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 media
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 modprobe.d
-rw-r--r--.  1 root   root      0 Apr 24 17:49 motd
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 motd.d
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 mount
drwx------.  2 root   root     40 Apr 24 17:49 multipath
drwxr-xr-x.  3 root   root     60 Apr 24 17:49 ostree
-rw-r--r--.  1 root   root    161 Apr 24 17:49 ostree-booted
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 pcscd
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 podman
-rw-------.  1 root   root     25 Apr 24 17:49 qga.state
-rw-r--r--.  1 root   root      0 Apr 24 17:49 rpc.statd.pid
drwx------.  2 rpc    rpc      40 Apr 24 17:49 rpcbind
-r--r--r--.  1 root   root      0 Apr 24 17:49 rpcbind.lock
srw-rw-rw-.  1 root   root      0 Apr 24 17:49 rpcbind.sock
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 samba
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 sepermit
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 setrans
-rw-------.  1 root   root      5 Apr 24 17:49 sm-notify.pid
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 ssh-unix-local
drwxr-xr-x.  2 root   root     40 Apr 24 17:49 sshd
-rw-r--r--.  1 root   root      5 Apr 24 17:49 sshd.pid
drwxrwxr-x.  2 sssd   sssd     40 Apr 24 17:49 sssd
drwx--x--x.  3 root   root     60 Apr 24 17:49 sudo
drwxr-xr-x. 23 root   root    660 Apr 24 17:49 systemd
drwxr-xr-x.  2 root   root     60 Apr 24 17:49 tmpfiles.d
drwxr-xr-x.  3 root   root     60 Apr 24 17:49 tpm2-tss
drwxr-xr-x.  8 root   root    180 Apr 24 17:49 udev
drwxr-xr-x.  4 root   root     80 Apr 24 17:49 user
-rw-rw-r--.  1 root   utmp   1536 Apr 24 17:49 utmp

find / -type d -name install -print
/sysroot/ostree/deploy/default/deploy/3db3bd964db49d23987553a2d286e058edc9f72868d07b944ee47463c4b3be05.0/usr/lib/bootc/install
/sysroot/ostree/repo/refs/heads/ostree/container/image/oci_3A__2F_run/install
/usr/lib/bootc/install

find / -type d -name repo -print
/sysroot/ostree/deploy/default/deploy/3db3bd964db49d23987553a2d286e058edc9f72868d07b944ee47463c4b3be05.0/sysroot/ostree/repo
/sysroot/ostree/repo
/sysroot/ostree/repo/refs/heads/ostree/container/image/oci_3A__2F_run/install/repo

[cgwalters]

This is a duplicate of osbuild/bootc-image-builder#780 I believe

[djarbz]

This is a duplicate of osbuild/bootc-image-builder#780 I believe

@cgwalters I'm not sure it is? That issue regards when a custom KS file is provided, which I did not.

[djarbz]

I checked the KS files in my ISO and that bootc switch command exists.

osbuild.ks

%include /run/install/repo/osbuild-base.ks

reqpart --add-boot

part swap --fstype=swap --size=1024
part / --fstype=ext4 --grow

reboot --eject
%post --erroronfail
bootc switch --mutate-in-place --transport registry ghcr.io/djarbz/<IMAGE>:<TAG>

# used during automatic image testing as finished marker
if [ -c /dev/ttyS0 ]; then
    # continue on errors here, because we used to omit --erroronfail
    echo "Install finished" > /dev/ttyS0 || true
fi
%end

osbuild-base.ks

ostreecontainer --url=/run/install/repo/container --transport=oci
rootpw --lock
lang en_US.UTF-8
keyboard us
timezone UTC
clearpart --all
network --device=link --bootproto=dhcp --onboot=on --activate

[cgwalters]

This needs debugging for sure, but it does have the same symptom, and regardless of anything else it'd be a bootc-image-builder bug today. There is nothing in bootc that references /run/install.

[averms]

I'm getting the same issue and I think this could be related to #931.

[djarbz]

I rebased on Fedora 41 and had no issues running bootc update --check or bootc update --apply.

[cgwalters]

I'm getting the same issue and I think this could be related to #931.

Thanks, yes. I think you're quite right there could be a bootc bug here. Let's continue to track in that issue.