Skip to content

bootc install to-filesystem does not check for mutable /usr before performing destructive operations #787

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
ryanabx opened this issue Sep 12, 2024 · 1 comment

Comments

@ryanabx
Copy link

ryanabx commented Sep 12, 2024

This isn't really a bug, just a behavior that probably needs to be documented or prevented outright.

To reproduce

  1. Have a Fedora Atomic system (with read-only usr)
  2. Run this command (from the documentation here):
sudo podman run --rm --privileged -v /dev:/dev -v /var/lib/containers:/var/lib/containers -v /:/target \
             --pid=host --security-opt label=type:unconfined_t \
             <image> \
             bootc install to-existing-root

Observe how your /boot drive will be wiped and then the installation will fail to run fchmod, my guess being due to the read-only /usr, aborting the installation.

@cgwalters
Copy link
Collaborator

This relates to e.g. #137

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants