doc/api-extensions: security.devlxd applies to both containers and VMs
#12747
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
It was likely introduced back when LXD only knew about containers. Signed-off-by: Simon Deziel <[email protected]>
github-actions
bot
added
Documentation
simondeziel
force-pushed
the
restrict-devlxd-instance
branch
from
9218dc4 to
0de644a
Compare
simondeziel
changed the title
security.devlxd applies to both containers and VMs
tomponline
approved these changes
Jan 18, 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.
It was likely introduced back when LXD only knew about containers.
This was tested by toggling
security.devlxdon a VM and an container. In both cases,/dev/lxd/sockvanishes whensecurity.devlxd=false.