Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

install: Drop code/test uses of --security-opt #930

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

cgwalters
Copy link
Collaborator

We think this is unnecessary now; part of improving
the ergonomics of bootc install in general, but
especially with the to-existing-root path.

Once this lands, at some point later then we
can also remove it from all of the documentation.
But the most safe thing is to leave it in the
docs for a bit longer.

Closes: #928

We're looking again at the ergonomics of `bootc install to-existing-root`.
This uses the "mounting into mount namespaces" from the new
mount API to automatically set up `/dev` and `/var/lib/containers`
if they weren't provided to `podman run`, which shrinks what's
needed a bit.

Closes: containers#826

Signed-off-by: Colin Walters <[email protected]>
Now that we unconditionally mount /var/lib/containers, drop
the hacky fork-skopeo-in-host-mountns code.

Signed-off-by: Colin Walters <[email protected]>
Keep the bind mounts in the docs though for now because many
people will be using the current docs with older bootc.

Signed-off-by: Colin Walters <[email protected]>
Build on our new logic for bind mounting from the host mountns
to also drop the need for the `-v /:/target` in the alongside
install code.

Signed-off-by: Colin Walters <[email protected]>
Hooray for `const`.

Signed-off-by: Colin Walters <[email protected]>
These should be unnecessary.

Signed-off-by: Colin Walters <[email protected]>
We think this is unnecessary now; part of improving
the ergonomics of `bootc install` in general, but
especially with the `to-existing-root` path.

Once this lands, at some point later then we
can also remove it from all of the documentation.
But the most safe thing is to leave it in the
docs for a bit longer.

Closes: containers#928

Signed-off-by: Colin Walters <[email protected]>
@cgwalters
Copy link
Collaborator Author

Depends on #919

@github-actions github-actions bot added the area/install Issues related to `bootc install` label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to `bootc install` do-not-merge/work-in-progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Investigate dropping requirement for --security-opt label=type:unconfined_t
1 participant