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

Enhance --link to connect to host's networks, and rewire ports #11247

Closed
dhbaird opened this issue Mar 9, 2015 · 8 comments
Closed

Enhance --link to connect to host's networks, and rewire ports #11247

dhbaird opened this issue Mar 9, 2015 · 8 comments
Labels
area/networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny

Comments

@dhbaird
Copy link

dhbaird commented Mar 9, 2015

In #1143, @altaurog proposed a --link-host option, which I'd like to resurrect for consideration, to link to host ports, with port number rewiring. At the moment, Ambassador provides this ability, but requires forwarding through a proxy (socat). Here's an example concept for --link-host:

docker run --link-host hostip:hostport:aliasport[:hostport:aliasport:...]:alias
# where hostip is any routable IP from the host, or 127.0.0.1 for localhost

There is an alternative practice of using --add-host=alias:$(hostip), but this practice doesn't address the port rewiring that could be required.

Thanks for your consideration.

@dhbaird dhbaird changed the title Enhance --link to connect to host's networks Enhance --link to connect to host's networks, and rewire ports Mar 9, 2015
@cades
Copy link

cades commented Apr 14, 2015

+1

@thaJeztah thaJeztah added Networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny labels Apr 14, 2015
@cusspvz
Copy link

cusspvz commented Apr 24, 2015

+1

2 similar comments
@lynchc
Copy link

lynchc commented Apr 27, 2015

+1

@chiavegatto
Copy link

+1

@thaJeztah
Copy link
Member

Not sure if this is going to be part of that (yet), but with the 1.7 release, there will also be "experimental" builds, to allow testing future features.

With the integration of libnetwork in Docker 1.7, there's work in progress for a Network-API, see this pull request for what's being worked on; #13441

@thaJeztah
Copy link
Member

I asked a maintainer of libnetwork if this scenario will be supported with the coming features and he added some additional information in a comment; #13441 (comment)

@mavenugo
Copy link
Contributor

Thanks @thaJeztah . I would recommend opening an issue in libnetwork & if there is enough interest, this feature can make it to appropriate drivers (inbuilt or external)

@LK4D4
Copy link
Contributor

LK4D4 commented Sep 15, 2016

links is not a way to make containers talk to each other now.

@LK4D4 LK4D4 closed this as completed Sep 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Projects
None yet
Development

No branches or pull requests

9 participants