Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fs: mount namespace within runsc doesn't seem to work #221

Closed
yoshiat opened this issue May 1, 2019 · 6 comments
Closed

fs: mount namespace within runsc doesn't seem to work #221

yoshiat opened this issue May 1, 2019 · 6 comments
Labels
area: compatibility Issue related to (Linux) kernel compatibility area: filesystem Issue related to filesystem priority: p2 Normal priority type: enhancement New feature or request

Comments

@yoshiat
Copy link
Collaborator

yoshiat commented May 1, 2019

From @AkihiroSuda here.
The context is that he has been looking into running BuildKit on UML/gVisor on Docker on real Linux kernel. And BuiltKit needs to invoke runc or gVisor. As running runc may require more syscalls (and options) to be supported, he thought BuildKit could run by replacing runc with unshare -m chroot if gVisor supports it.

$ docker run -it --rm --runtime=runsc alpine \
/ # unshare --uts --ipc --net --pid --user echo hi \
hi
/ # unshare --mount echo hi
unshare: can't mount none on / (flags:0x44000): Bad address
/ #

Before going down this path, he got stuck with the lack of MS_BIND|MS_REC support which should be tracked in #179.

@amscanne
Copy link
Contributor

amscanne commented May 1, 2019

Yes, most other namespaces are implemented but not mount namespaces. It will follow after the major file system refactor in progress.

@prattmic prattmic added area: compatibility Issue related to (Linux) kernel compatibility area: filesystem Issue related to filesystem type: enhancement New feature or request labels May 1, 2019
@ianlewis ianlewis added the priority: p2 Normal priority label May 3, 2019
@pkit
Copy link
Contributor

pkit commented Jul 8, 2022

vfs2 is the default. Can it be implemented now? I can poke it, if needed.

@kevinGC
Copy link
Collaborator

kevinGC commented Jul 13, 2022

@nixprime WDYT?

@pkit
Copy link
Contributor

pkit commented Jul 16, 2022

@kevinGC it seems like it has some TODO here

mntnsVFS2 := t.mountNamespaceVFS2

@pkit
Copy link
Contributor

pkit commented Jul 16, 2022

Ah, bind mounts are not there too. Probably needs bind mounts first...

@avagin
Copy link
Collaborator

avagin commented Aug 15, 2024

Fixed by 41bb04c.

@avagin avagin closed this as completed Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: compatibility Issue related to (Linux) kernel compatibility area: filesystem Issue related to filesystem priority: p2 Normal priority type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants