install: Drop code/test uses of --security-opt
#930
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Depends on #919 |
cgwalters
force-pushed
the
tree-wide-security-opt
branch
from
6b62ba1 to
bcdac01
Compare
|
Rebased 🏄 |
|
Conflicts |
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
force-pushed
the
tree-wide-security-opt
branch
from
bcdac01 to
fa474a9
Compare
omertuc
approved these changes
Dec 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We think this is unnecessary now; part of improving
the ergonomics of
bootc installin general, butespecially with the
to-existing-rootpath.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