Investigate dropping requirement for --security-opt label=type:unconfined_t
#928
Labels
area/install
Issues related to `bootc install`
Comments
cgwalters
added a commit
to cgwalters/bootc
that referenced
this issue
Dec 2, 2024
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
added a commit
to cgwalters/bootc
that referenced
this issue
Dec 9, 2024
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
added a commit
to cgwalters/bootc
that referenced
this issue
Dec 10, 2024
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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moving this from #826 (comment)
Basically it'd be nice if we could simplify the install invocations and drop
--security-opt label=type:unconfined_t. In some testing, it works fine without it with a Fedora 40 host (podman machine40.20241019.2.0,podman version 5.2.5). It also works on a C9S host (podman-5.3.1-1.el9.x86_64).Actually, things also work with
podman version 4.9.4-rhelfrom RHEL 9.4.Soo...yeah, let's try just taking this out of all of our CI and see if anything breaks.
The text was updated successfully, but these errors were encountered: