Add --pid flag for staying in the host's pid namespace#10080
Add --pid flag for staying in the host's pid namespace#10080crosbymichael merged 2 commits intomoby:masterfrom
Conversation
We want to be able to use container without the PID namespace. We basically want containers that can manage the host os, which I call Super Privileged Containers. We eventually would like to get to the point where the only namespace we use is the MNT namespace to bring the Apps userspace with it. By eliminating the PID namespace we can get better communication between the host and the clients and potentially tools like strace and gdb become easier to use. We also see tools like libvirtd running within a container telling systemd to place a VM in a particular cgroup, we need to have communications of the PID. I don't see us needing to share PID namespaces between containers, since this is really what docker exec does. So currently I see us just needing docker run --pid=host Docker-DCO-1.1-Signed-off-by: Dan Walsh <dwalsh@redhat.com> (github: rhatdan)
Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
|
kewl LGTM, I bet next will come |
|
This has been LGTM'ed in the other PR, merging. |
Add --pid flag for staying in the host's pid namespace
|
I just shed of tear of joy when I noticed this PR was merged. I'll be a sobbing baby when |
|
Is there a PR open for --pod=container ?
|
|
I was making a joke that it would be next, but no one has made it yet On Thursday, January 15, 2015, Tim Hockin notifications@github.com wrote:
|
|
Consider this a request?
|
|
@thockin @ibuildthecloud it looks like you both have use-cases to describe why it's useful. Could you please create a new issue describing this? It'd make it easier to track, and a decision to implement it (or not) can be made there. (Sorry for meddling in this, @jfrazelle 😄 trying to keep my head sane following things) |
|
I cannot seem to figure out how start a container with |
Replaces #9339
This adds an integration test for the --pid host mode