Closed cpuguy83 closed 10 years ago
BTW, I know @crosbymichael is working on stuff to enable setting network interfaces with libcontainer directly from the docker run command so I'm not sure how much effort should be put into this.
Though on 0.9 I'm currently SOL on getting a public IP into my container (because LXC isn't working for me on 0.9, https://github.com/dotcloud/docker/issues/4584 )
I think all he needs to do is find the pid for the namespace. All the information that pipework should need is found in:
/var/lib/docker/execdriver/native/<id>/{pid, container.json}
Thanks!
Working on this now.
(Associated PR is #41)
Does PR #41 resolve this issue? Is pipework ready for libcontainer in production?
@bretttrotter-wf Yes, this is all taken care of.
So far the issue just seems to be that pipework can't find the cgroup the container is in via line 87:
NN=$(find "$CGROUPMNT" -name "$DOCKERID" | wc -l)
And indeed the containers don't seem to have anything in there anymore.This is about as far as I've gotten. Looked at some of the libcontainer code to figure this out but nothing really stood out to me.