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

runc to support setns(pid) and share(new pid) together #2649

Open
xiechao4 opened this issue Oct 15, 2020 · 0 comments
Open

runc to support setns(pid) and share(new pid) together #2649

xiechao4 opened this issue Oct 15, 2020 · 0 comments

Comments

@xiechao4
Copy link

hi
I want to support quick launch and sharing between processes in cloud.
The case likes: All process in the cloud will load many files and do some initialization for example the JAVA class loading. So i want to setup a container named zygote container which contains the already initialization process named Zygote. When someone request a new application, a application container will be setup and request the zygote container to fork a process, this process will be forked by Zygote and moved to the application container to run the requested application.
Because process can only be setns to pid namespace following parent->child->grandchild, i set up application container wtih --pid=zygote container. It makes that application container share same pid namespace with zygote container. This will make application container not be private, for example not correct init process in application container.
i want to make zygote container pid namespace to be parent of application container pid namespace as below
application 1 container
^
|
| child
|
zygote container
|
| child
|
v
application 2 container

Current runc implementation support container to enter someone's namespace, but do not support new pid namespace by share after enter someone's pid namespace.
How can i do that or there are something i misunderstand.

Thanks

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

No branches or pull requests

1 participant