Problem enabling transient /etc in fedora-based bootc image: rpm-ostree-fix-shadow-mode.service failed #1435
Replies: 2 comments 1 reply
-
We're going to fix this soon, it is a recent regression ostreedev/ostree#3476 |
Beta Was this translation helpful? Give feedback.
-
Hello again @cgwalters, it appears that transient etc still doesn't work, but for a different reason. The ostree patch has resolved the OS not being able to boot, however upon booting two systemd units relating to bootc and its ecosystem fail (in order):
After investigating a bit on my end, the only error message I was able to extract was the following: [root@fedora]# rpm-ostree fix-shadow-perms
error: Remounting /boot read-write: Invalid argument The same error appears when executing [root@fedora] # bootc upgrade --apply
error: Upgrading: Initializing storage: Acquiring sysroot: Remounting /boot read-write: Invalid argument From what I gathered it looks more like an argument parsing issue than an actual /boot mount error. Digging into the rpm-ostree source code, the only place I think the error may be coming from is in the "fix_shadow_perms_entrypoint" function of the passwd.rs file. I stopped looking there, as that function calls some low level C/C++ bindings. Additional information: Fedora version: 42 Would it be possible for your team to investigate on your end? /etc is crucial for us, and it is strongly recommended in your documentation. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am trying to enable transient /etc in my bootc image build, however it doesn't seem to work.
I have followed the documentation, and implemented the example from the gitlab repository, as well as read a bunch of issues/discussions more or less relating to my problem.
Here is my Containerfile:
My local root/ directory contains the ostree configuration (with transient etc enabled) and a few configuration files relating to the creation of a development user, including an authorized ssh key, sysusers.d file and a systemd unit responsible for chowning the developer's home directory.
I generate the base install image using bootc-image-builder, with the qcow2 format, and run the VM using virt-manager.
Upon launch, my VM enters recovery mode, and the generated /run/initramfs/rdsosreport.txt file doesn't seem to contain any useful information (at first glance).
Here's a screenshot of the VM:
Journal logs show that the "ostree-prepare-root" service has failed; it can't seem to create the /run/os directory:
Going back to the Containerfile build, dracut seems to have an error, but generates the initramfs image anyways:
This is a very strange bug, and as far as I know does not seem to come from my configurations. Hopefully that's not true :).
Any help is greatly appreciated, thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions