Skip to content

Conversation

@wking
Copy link
Contributor

@wking wking commented May 24, 2016

The user-namespace restriction isn't about the root filesystem in particular. For example, if you bind mount in a second filesystem, the runtime shouldn't adjust ownership on that filesystem either.

I've also adjusted the old “permissions” to “ownership”, since that more clearly reflects the fields (user and group) that you would modify if you wanted to adjust for user namespacing.

This nibbles some more ground-work off from #423, since that approach worked well in #435.

The user-namespace restriction isn't about the root filesystem in
particular.  For example, if you bind mount in a second filesystem,
the runtime shouldn't adjust ownership on that filesystem either.

I've also adjusted the old "permissions" to "ownership", since that
more clearly reflects the fields (user and group) that you would
modify if you wanted to adjust for user namespacing.

Signed-off-by: W. Trevor King <[email protected]>
@crosbymichael
Copy link
Member

LGTM

1 similar comment
@mrunalp
Copy link
Contributor

mrunalp commented May 24, 2016

LGTM

@mrunalp mrunalp merged commit 878fac1 into opencontainers:master May 24, 2016
@wking wking deleted the do-not-modify-filesystem-owners branch May 24, 2016 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants