Requests to docker-machine created boot2docker host

For fast development purposed I spin a MongoDB container on boot2docker on the standard MongoDB port and then I just connect to the database on the boot2docker ip on that port. Currently its

192.168.59.105:27017

With docker-machine I created a new boot2dockers named “host” which has the ip 192.168.99.113 where I installed docker-compose to spin MongoDB + a data container. But contrary to the default boot2docker, I cant seem to connect to Mongo on that machines ip (I get the ip with docker-machine ip host)

  • permission denied error in docker
  • Reuse existed containers upon Docker service scale [swarmkit]
  • Installing docker on azure virtual machine windows 10
  • Docker daemon running under SSL contacted using cURL
  • How to forward Docker for Mac to X11?
  • how can I set the working directory in old version of docker in the run command?
  • 192.168.99.113:27017
    

    In this case I don’t get a connection, I don’t even see the MongoDB warning message when I put that address on Chrome. Am I missing some critical configuration step to make this happen?

  • How to link binaries between docker containers
  • Docker cp error: Path not specified
  • How to efficiently manage docker storage drive in Centos 7
  • how to pass command line arguments to a python script running in docker
  • How to run a Shiny docker container on Alpine Linux?
  • Cant push docker image to local registry by .sh script called from plink - no basic auth credentials
  • One Solution collect form web for “Requests to docker-machine created boot2docker host”

    Create a port forwarding for port 27017 in VirtualBox for your docker-machine named host.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.