Antonio Murdaca

> in current Fedora and C10S I think we can just drop the `ssh_keys` group from the base image. @cgwalters to go ahead with this, at least from the ssh...

@cgwalters alrighty, I'll try to narrow it down and provide more info (and yeah, super annoying to test and iterate for a bug like this)

> I think it's one of the packages there ~~so, the specific error thrown, if we look at the osbuild stage source, points to the fact that there's no selinux...

the transaction on the -dev container is this one and flatpak-selinux is there ``` bash-5.1# rpm-ostree install gnome-kiosk-script-session Enabled rpm-md repositories: copr-coreos-continuous copr-rhcontainerbot-bootc extras-common baseos appstream Updating metadata for 'copr-coreos-continuous'......

> ``` > $ truncate -s 10G ~/build/fedora-bootc.raw; podman run -ti --pull=newer --rm --privileged --pid=host --security-opt label=type:unconfined_t -v /var/lib/containers:/var/lib/containers -v /var/home/walters/build:/output quay.io/cgwalters/ostest bootc install to-disk --via-loopback --skip-fetch-check --generic-image /output/fedora-bootc.raw >...

@achilleas-k following https://github.com/osbuild/bootc-image-builder/issues/186 I've narrowed this issue down to just BIB as it just works with bootc self-install as reported above. This is the minimal Containerfile that I've used (the...

I’ll check it out, maybe composefs? ~~Although, what is greenboot exit code 4 too? @say-paul~~

This may be relevant https://github.com/ostreedev/ostree/issues/3193#issuecomment-2578264200 @mcattamoredhat do you know what exactly changed in the new snapshot? rpm-ostree? Just ostree? Can you print versions and also provide the content of /etc/fstab...

it seems that changes in https://github.com/osbuild/osbuild-composer/pull/4569/files are tests only, so how did you reproduce this @mcattamoredhat ? 🤔 I'm trying with 9.6 nightlies repo enabled, building a commit and upgrade...

since `ostree.sh` uses anaconda, this may be relevant https://bugzilla.redhat.com/show_bug.cgi?id=2332319 if we understand it's systemd-remount-fs.service that it's causing this issue (still not sure and I say this because there's no bootc...