Integrate pipework in to the docker
nadrimajstor opened this issue ยท 6 comments
๐
I approve; but there is no actionable item there... So I'll close the issue. (Trying to keep only actionable issues open, as much as possible! :-))
Thanks anyway for your interest!
Thank you for creating the pipework. ๐
It works flawlessly for exposing the lead container via macvlan.
I was thinking that this one might get flagged as a feature request and become a pingback for lazy beep that I am. ๐
Understood :-)
Don't worry, I think you'll hear about it when Docker gains extra network
powers!
Cheers,
On Thu, Sep 18, 2014 at 1:11 PM, Ivan Pejiฤ notifications@github.com
wrote:
Thank you for creating the pipework. [image: ๐]
It works flawlessly for exposing the lead container via macvlan.
I was thinking that this one might get flagged as a feature request and
become a pingback for lazy beep that I am. [image: ๐]โ
Reply to this email directly or view it on GitHub
#88 (comment).
@jpetazzo https://twitter.com/jpetazzo
Latest blog post:
http://jpetazzo.github.io/2014/06/23/docker-ssh-considered-evil/
FYI:
With docker 1.5.0, I have been able to put pipework into a container. So that it can run alongside your other containers. You can find it on docker hub as the dreamcat4/pipework docker image. Or just search for "pipework" on docker hub.
@dreamcat4 Have I got this right: Its a privileged container that sets up network for other containers?
@nadrimajstor Yes. That is 100% correct.