gofer: open volumes from the initial userns #11118
Open
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
copybara-service bot
pushed a commit
that referenced
this pull request
Nov 5, 2024
when gofer can't open them from its user namespace. The gofer namespace can have custom user/group mappings that can prevent it to access volumes. This change repeats the behaviour of runc. If we can't open a volume from the gofer userns, we are trying to open it from the initial userns. For that, we create a small rpc server that the gofer communicates with. FUTURE_COPYBARA_INTEGRATE_REVIEW=#11118 from avagin:gofer-vs-userns d2de7c9 PiperOrigin-RevId: 693124536
avagin
force-pushed
the
gofer-vs-userns
branch
from
d2de7c9
to
03ea43b
Compare
when gofer can't open them from its user namespace. The gofer namespace can have custom user/group mappings that can prevent it to access volumes. This change repeats the behaviour of runc. If we can't open a volume from the gofer userns, we are trying to open it from the initial userns. For that, we create a small rpc server that the gofer communicates with. Signed-off-by: Andrei Vagin <[email protected]>
avagin
force-pushed
the
gofer-vs-userns
branch
from
03ea43b
to
50fd999
Compare
copybara-service bot
pushed a commit
that referenced
this pull request
Nov 5, 2024
when gofer can't open them from its user namespace. The gofer namespace can have custom user/group mappings that can prevent it to access volumes. This change repeats the behaviour of runc. If we can't open a volume from the gofer userns, we are trying to open it from the initial userns. For that, we create a small rpc server that the gofer communicates with. FUTURE_COPYBARA_INTEGRATE_REVIEW=#11118 from avagin:gofer-vs-userns 50fd999 PiperOrigin-RevId: 693124536
copybara-service bot
pushed a commit
that referenced
this pull request
Nov 5, 2024
when gofer can't open them from its user namespace. The gofer namespace can have custom user/group mappings that can prevent it to access volumes. This change repeats the behaviour of runc. If we can't open a volume from the gofer userns, we are trying to open it from the initial userns. For that, we create a small rpc server that the gofer communicates with. FUTURE_COPYBARA_INTEGRATE_REVIEW=#11118 from avagin:gofer-vs-userns 50fd999 PiperOrigin-RevId: 693124536
copybara-service bot
pushed a commit
that referenced
this pull request
Nov 5, 2024
when gofer can't open them from its user namespace. The gofer namespace can have custom user/group mappings that can prevent it to access volumes. This change repeats the behaviour of runc. If we can't open a volume from the gofer userns, we are trying to open it from the initial userns. For that, we create a small rpc server that the gofer communicates with. FUTURE_COPYBARA_INTEGRATE_REVIEW=#11118 from avagin:gofer-vs-userns 50fd999 PiperOrigin-RevId: 693124536
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.
when gofer can't open them from its user namespace. The gofer namespace can have custom user/group mappings that can prevent it to access volumes.
This change repeats the behaviour of runc. If we can't open a volume from the gofer userns, we are trying to open it from the initial userns. For that, we create a small rpc server that the gofer communicates with.