Skip to content

Conversation

@nirped
Copy link
Contributor

@nirped nirped commented Dec 4, 2015

When using the Docker multi-host networking, IPAddress under NetworkSettings is set to an empty string and the container IP can be retrieved from NetworkSettings.Networks.

At this point it is assumed a single Docker network is associated with the container

When using the Docker multi-host networking, IPAddress under NetworkSettings is set to an empty string and the container IP can be retrieved from NetworkSettings.Networks.

At this point it is assumed a single Docker network is associated with the container
@Govinda-Fichtner
Copy link

+1 Can I help somehow to get this merged?

@progrium
Copy link
Contributor

progrium commented Jan 4, 2016

Can I get some verifications that this is a good and working PR?

@MBuffenoir
Copy link

I will try to build an image and test it ... that's a needed feature 👍

@SirIle
Copy link

SirIle commented Jan 5, 2016

I have been using an image by kidibox (kidibox/registrator) with this pull request merged and it has worked as it should with overlay networking with the "-internal" flag. The problem is that an unnecessary number of ports (all that are EXPOSEd in the Dockerfile) get registered, some way to better control the ports would be preferred. Maybe a environment variable would do?

@progrium
Copy link
Contributor

progrium commented Jan 5, 2016

Definitely sounds like more configuration is necessary for that use case, but that would be a separate issue/PR. I'll merge and if there are problems somebody please reopen.

progrium added a commit that referenced this pull request Jan 5, 2016
Support for Docker multi host networking
@progrium progrium merged commit a0d2931 into gliderlabs:master Jan 5, 2016
This was referenced Jun 25, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants