4 ms·
I still don't know how to give docker an IP address or "physical" network card on my network. I was able to do this very easily with solaris zones, and even BS
by dijit 11y ago
I still don't know how to give docker an IP address or "physical" network card on my network.
I was able to do this very easily with solaris zones, and even BSD jails, but every installation of docker that is any way integrated into packages seems to be unable to do this.
perhaps I'm simply not using the right google search terms.
- mrala 11y agohttps://docs.docker.com/engine/userguide/networking/dockernetworks/ https://docs.docker.com/engine/userguide/networking/dockerne...
- dijit 11y agoThis doesn't really help, exposing network ports is not the same as giving a container a seperate IP address.
- mrala 11y agoIs this what you're looking for? https://github.com/docker/docker/pull/19001 https://github.com/docker/docker/pull/19001
- dijit 11y agoYep. Glad to see it was merged. I wonder when it will trickle down into my distro of choice. :)
- Patrick_Devine 11y agoYou should check out get.docker.com. Most of the distro versions are pretty old/broken.
- general_failure 11y agoIs your intention to expose the ports of a docker container? If you want to do this search for "expose" ports. The docker run option is -p and -P for this. Or to create a subnet with custom IP for the docker daemon's bridge network? Use -b option to docker daemon. https://docs.docker.com/engine/userguide/networking/ https://docs.docker.com/engine/userguide/networking/ is a good place to start. If you have a specific question, feel free to ask and I can try to answer.
- dijit 11y agono, that's not my intention, my intention is to not have to deal with iptables mangling packets and adding netfilter tags to everything. not to mention port collisions with things that must run on predefined ports (think SMTP or pesky applications that keep redirecting you back to port 80) I'm looking to expose 'an IP' similar to a bridged/open network in KVM.
- cgb_ 11y agoI've found pipework (https://github.com/jpetazzo/pipework https://github.com/jpetazzo/pipework) still to be the easiest way to manage networking in containers when you know what you want. Start up your container with --net=none and then something like: pipework mybr01 mycontainername 1.1.1.3/24@1.1.1.1 Docker 1.9's enhanced networking functionality is supposed to make this easier, although I've had a hard time understanding how to use it on my preferred RHEL/CentOS platform (the doco I've read either glosses over details or assumes you use docker-machine & swarm, neither of which I want to use in a simple deployment). Weave is supposed to make this easy to (and offers some simplicity over docker 1.9's requirement for a clustered key-value store), but I got frustrated at their implicit iptables nat rule for networks created by default and haven't worked out how to stop that.
- AnythingForDogs 11y agoTake a look at Calico - https://github.com/projectcalico/calico-containers https://github.com/projectcalico/calico-containers It's a networking solution that uses BGP to connect containers across multiple hosts, and so can very easily integrate with existing infrastructure.
- NetStrikeForce 11y agoI haven't tried it yet with Docker, but I'm starting a networking service (pretty much SoftEther as a service) that might work on your case. The idea is that your Docker containers will connect to a central server (443/TCP outgoing traffic) and have a virtual private network among them through this "hub", so they've got full access to each other. This is a layer 2 network and in my offering I have DHCP running by default to simplify things (100.64.0.0/24... naughty, I know :)). The communications are encrypted, so effectively you've got a sort of Virtual Private Network between your containers. As I said, I haven't tried yet with Docker, but it's worth a shot. My service simplifies the process of getting up and running. https://wormhole.network https://wormhole.network
- clinta 11y agoI've had the same struggle. I'm moving my network to use a vxlan overlay for VMs so I ended up building a vxlan driver for docker networking which lets me do the same thing for containers. That project is here: https://github.com/clinta/docker-vxlan-plugin https://github.com/clinta/docker-vxlan-plugin Docker seems really intent on NATing containers behind the host, which IMO is not acceptable from a security perspective when I want to firewall outbound access based on a containers role. Kubernetes is another option which creates a unique IP per container pod on the same network as the host. Not as flexible as a vxlan approach where containers can be micro-segmented into specific networks, but more like BSD jails that you're used to.
- NetStrikeForce 11y agoI did this now: https://github.com/pjperez/docker-wormhole https://github.com/pjperez/docker-wormhole Example Docker images for iPerf client and server: https://github.com/pjperez/docker-iperfserver https://github.com/pjperez/docker-iperfserver https://github.com/pjperez/docker-iperfclient https://github.com/pjperez/docker-iperfclient Edit to clarify: You can deploy each of the above images on different hosts located on different providers. There's no need for the hosts to have visibility between each other at all.