[Feature] Add container launched with --net=host about registrator HOT 13 CLOSED

Can you give me a more detailed example scenario of what it would look like
and do?

On Tue, Sep 9, 2014 at 4:20 AM, Miguel Angel Guillén <
[email protected]> wrote:

I have a couple of containers that are launched with --net=host, by
default registrator only add to consul container with exposed ports but
could be a very helpful to add support for containers with the host net
option, maybe adding a env variable (like the exposed port) for registrator
get the values to register in consul.

—
Reply to this email directly or view it on GitHub
https://github.com/progrium/registrator/issues/19.

Jeff Lindsay
http://progrium.com

from registrator.

Yes, I have some containers that they need to run with net=host because uses scala+akka app and akka don't support port redirection (thats why I need to launch with this param) but I have another container (nginx) that need to get in consul a list of this apps to proxy them but because they are not been registered because they are launched with net=host param

from registrator.

It seems like you can just manually set the ports the same on the host
interface without using net=host ... alternatively you can use ambassadord
to route to the right port. Because of those workarounds and not a lot of
demand, this feature is likely to stay deprioritized for a while.

On Tue, Sep 9, 2014 at 10:14 AM, Miguel Angel Guillén <
[email protected]> wrote:

Yes, I have some containers that they need to run with net=host because
uses scala+akka app and akka don't support port redirection (thats why I
need to launch with this param) but I have another container (nginx) that
need to get in consul a list of this apps to proxy them but because they
are not been registered because they are launched with net=host param

—
Reply to this email directly or view it on GitHub
https://github.com/progrium/registrator/issues/19#issuecomment-54984426.

Jeff Lindsay
http://progrium.com

from registrator.

I'm warming up to this feature. Just requires some more thought to implement it. I agree that if you use net=host then your services should still be registered...

from registrator.

#64 fixing this issues or not? Could you check the pull request?

from registrator.

One of the changesets in #64 should solve this feature request. I had the same problem with Apache Mesos that needs net=host. The docker metadata is slightly different for a net=host container. Notably the NetworkSettings.Ports section isn't populated. However the same info is in HostConfig.Ports if you specify e.g. "--net=host -p 5050". #64 adds support for defaulting to HostConfig.Ports if there are no matching port in NetworkSettings.Ports

from registrator.

It will be great when we get this fix , this issue super important for example, in case you want to improve your network performance : redis , db etc ... Docker suggest to work net=host.

Please merge this fix ASAP :)
Thanks.

from registrator.

Indeed, It appear that some workload could benefit from running with --net=host. Workloads with high packet rates would avoid some overhead.

Reference ( figure 13,14 and surrounding text ) :
http://domino.research.ibm.com/library/cyberdig.nsf/papers/0929052195DD819C85257D2300681E7B/$File/rc25482.pdf

At the moment, the only workaround ( I can think of ) to benefit from --net=host in a registrator/consul.io setup is to run consul agent directly in the docker that need to register. But this is far from ideal.

👍

from registrator.

Why it is impossible to push the fix?

On 12 בדצמ׳ 2014, at 19:01, pfcarrier [email protected] wrote:

Indeed, It appear that some workload could benefit from running with --net=host. Workloads with high packet rates would avoid some overhead.

Reference ( figure 13,14 and surrounding text ) :
http://domino.research.ibm.com/library/cyberdig.nsf/papers/0929052195DD819C85257D2300681E7B/$File/rc25482.pdf

At the moment, the only workaround ( I can think of ) to benefit from --net=host in a registrator/consul.io setup is to run consul agent directly in the docker that need to register. But this is far from ideal.

—
Reply to this email directly or view it on GitHub.

from registrator.

+1

from registrator.

Any news ?

from registrator.

Whats the status of it? --net=host -p XXXX would be ok to use I guess. Fix still not merged?

from registrator.

Merged.

from registrator.