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

Allow joining cgroups of another container #68

Closed
mrunalp opened this issue Jul 10, 2015 · 6 comments
Closed

Allow joining cgroups of another container #68

mrunalp opened this issue Jul 10, 2015 · 6 comments

Comments

@mrunalp
Copy link
Contributor

mrunalp commented Jul 10, 2015

The spec allows specifying namespace fds via paths and that feature allows one container to share the namespaces of another container. Another feature to make that more useful is allowing a container to join the cgroups of another container using its pid. This will make it possible for higher level tooling to add nsinit/nsenter like functionality.

@crosbymichael @philips WDYT?

@philips
Copy link
Contributor

philips commented Jul 28, 2015

Why not use the cgroup name?

@mrunalp
Copy link
Contributor Author

mrunalp commented Jul 28, 2015

@philips That works, too. I think there should be a way to solve the use case.

@philips
Copy link
Contributor

philips commented Jul 28, 2015

@mrunalp Wait, sorry, what information would you add on top of the kernel metadata? e.g. /proc/571/cgroup

@wking
Copy link
Contributor

wking commented Sep 6, 2015

On Tue, Jul 28, 2015 at 12:05:54PM -0700, Brandon Philips wrote:

@mrunalp Wait, sorry, what information would you add on top of the
kernel metadata? e.g. /proc/571/cgroup

In the absence of further information here, I think we can close this
issue once #137 lands.

@mrunalp
Copy link
Contributor Author

mrunalp commented Sep 8, 2015

Yes, we can close this with #137.

@wking
Copy link
Contributor

wking commented Sep 29, 2015

#137 has landed. Close?

@vbatts vbatts closed this as completed Sep 29, 2015
@wking wking mentioned this issue Mar 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants