You can use rancher to solve 2., as it automatically manage IP addresses using IpSec private network. I guess kubernetes also solve problem no. 2.
Docker data volumes is living within the host or boot2docker on the local VM(boot2docker).
Having big data from mongoDB running in a data container and mongoDB in another seems to be the way. Will this scale on Google Cloud Engine or Azure Virtuel Machines or other. I mean if all this is running within ONE Virtuel Machine, like boot2docker or other in the cloud. Normally you would scale VM's by creating new instances of VM's but how is this possible with Docker?
Sorry to ask this on StackExchange, but there is no category on dba - but StackExchange has a Category for Docker.
docker create -v /some/directory mydatacontainer debian
This command tells Docker to create a new container named mydatacontainer based on the Debian Docker image. (You could use any of Docker’s other OS images here, too.) Meanwhile, the -v flag in the command above sets up a storage container in the directory /some/directory inside the container.
To repeat: That means the data is stored at /some/directory inside the container called mydatacontainer — not at /some/directory on your host system.
The beauty of this, of course, is that we can now write data to /some/directory inside this container, and it will stay there as long as the container remains up.
You can use rancher to solve 2., as it automatically manage IP addresses using IpSec private network. I guess kubernetes also solve problem no. 2.