jeroenpeeters/docker-network-containers

Scripts for setting up Docker router containers for exposing an other container's service on a public IP

docker-network-containers's Issues

Mac OSX?

This is more a question than an issue, but has anybody been able to get this to work on OSX? When running it I get the error "I do not know how to setup interface en0.". Then it continues on with "waiting for public ip to be bound" which never completes.

dhclient version 4.3.1?

It looks like the latest version of the container uses dhclient 4.3.1, which doesn't allow the '-H' option:

bash-4.3# dhclient -H foo eth1
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Usage: dhclient [-4|-6] [-SNTPI1dvrxi] [-nw] [-p <port>] [-D LL|LLT]
                [-s server-addr] [-cf config-file]
                [-df duid-file] [-lf lease-file]
                [-pf pid-file] [--no-pid] [-e VAR=val]
                [-sf script-file] [interface]

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

exiting.

Not sure if this is a dhclient bug (in which case, can we roll back), or intended behavior going forward (which would be annoying because providing the client hostname via dhclient is pretty standard afaik)

question wrt use with Kubernetes

This might not be applicable, but I thought I would ask. I've been using your network-containers for a while now, with great success (thanks BTW).

I've started working with Kubernetes so I'm still in the absorbing information stage, but I do have a small POC cluster running.

My issue is that I still need the functionality that your network-containers provide - meaning, I need to connect certain container types to the corporate network so that they can obtain DHCP addresses, be "publicly" available, etc...

At any rate, have you looked at running your network-containers from within the Kubernetes framework (given that it launches uses a shell script) or is it just not applicable, since it seems like you should be able to use one of the network overlay frameworks to achieve the same functionality?

Thanks! Yours is the ONLY one that works!

I tried a number of other ones, and yours is the ONLY one that works. How do you do that sorcery? I looked around and couldn't wrap how you are doing things.

Thomas