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)

  • Docker private registry can't find tags when pulling
  • Docker volume data does not get saved to host folder in mac
  • Caching Maven parent in offline build
  • How to connect to a dockerized PostgreSQL from (an undockerized) Python app
  • Not able to see STDERR Output with docker
  • Does hub.docker.com use “--no-cache” for automated builds?
  • 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?

  • View files in docker container
  • docker stack deploy do not remove services that are not declared in the current yaml compose file
  • cannot run jfrog executable from inside alpine linux container
  • What are possible STATUS of docker nodes?
  • ElasticBeanstalk: storing a bullet proof docker container
  • Docker composer copy files
  • 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.