jpetazzo / pipework

Software-Defined Networking tools for LXC (LinuX Containers)
Apache License 2.0
4.22k stars 727 forks source link

Integrate pipework in to the docker #88

Closed nadrimajstor closed 10 years ago

nadrimajstor commented 10 years ago

:+1:

jpetazzo commented 10 years ago

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!

nadrimajstor commented 10 years ago

Thank you for creating the pipework. :bow: 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. :blush:

jpetazzo commented 10 years ago

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: :bow:] 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: :blush:]

— Reply to this email directly or view it on GitHub https://github.com/jpetazzo/pipework/issues/88#issuecomment-56095094.

@jpetazzo https://twitter.com/jpetazzo Latest blog post: http://jpetazzo.github.io/2014/06/23/docker-ssh-considered-evil/

dreamcat4 commented 9 years ago

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.

nadrimajstor commented 9 years ago

@dreamcat4 Have I got this right: Its a privileged container that sets up network for other containers?

dreamcat4 commented 9 years ago

@nadrimajstor Yes. That is 100% correct.