Hi!
I have a server running docker (stand alone) and about 5 network cards, each one with their own network address/mask.
It’s possible to connect a container to specific network card, without need to set network address/netmask in docker?
I mean, in docker network type macvlan I must specify a network/netmask, but I don’t want to enable DHCP in docker, I already have DHCP running in this network…I just want the container to by-pass directly to this network (let’s say it’s in eth3 from server cards).
Also, it’s possible to have multiple networks on the same container, like VLAN’s? I would like to access multiple networks (already configured in server running docker) in my container.
There is no way to deactivate ipam for macvlan child interfaces. We had a similar query in the past. The final post points to an open GitHub issue about the topic:
When a container is created, it needs to know its network namespaces, before it starts the entry point script which eventually starts the main process. I am not sure how good the ipam concept, that request an ip that must remain valid during the lifecycle of a container, fits in with dhcp and its leases.
Of course one could prepare images to run a dhcp client as process along sine the main process, and require the container to be started as root and have the NET_ADMIN capability… Basically this would mean: say goodbye to running containers based on arbitrary images from a container registry as DockerHub.
This use case looks better suited for LXC containers.