pipework

I've found 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 th

I, too, had the idea of utilizing Docker in the IoT - in fact, I chose that as the focus of my MSc dissertation (though my primary goal was to implement automated docker/LXC container provisioning for resources on a server to be utilized by a sensor device). I created a little open-source tool called Orchestrator (https://github.com/cvlc/orchestrator) to automatically provision docker instances on a remote server in response to DHCPv6 requests. Unfortunately, I've been side-tracked on other projects for a while and haven't really got the ball rolling yet - I'll be looking to update it fairly soon, though! Jérôme Petazzoni (employee of Docker, formerly dotcloud) has created an excellent (I'd say essential) tool for dealing with networks under Docker called Pipework (https://github.com/jpetazzo/pipework) which is definitely worth a look if

This might be interesting too: Pipework https://github.com/jpetazzo/pipework Essentially it lets you create private networks between containers which could each run its own service (one for Postgres, one for Redis, etc).