Docker container – how to configure so it gets a viable IP address when running in vagrant?

Docker ( looks terrific. However, after installing VirtualBox, Vagrant
… and finally Docker on a Mac, I’m finding it’s not possible to access the service running in the Docker container from another computer (or from a terminal session on the Mac). The service I’m trying to access is Redis.

The problem appears to be that there’s no route to the IP address assigned to the Docker container. In this case the container’s IP is while the Mac’s IP is

  • How to log all the processes running inside a Docker container?
  • Enable Jenkins to export build artifact from Docker build environment
  • Easy, straightforward, robust way to make host port available to Docker container?
  • Is it possible to run kubernetes as a docker container?
  • How to mount HDFS in a Docker container
  • docker with shared folder d drive
  • A couple notes:

    1. It IS possible to access it – but only from within the VirtualBox session. This can be done using redis-cli -h -p 6379.
    2. I have added “ :bridged” to the VagrantFile in an attempt to get the, but that didn’t solve the problem.

  • Unable to connect to socket server running inside docker container
  • How do you deploy a docker image into Cloud Foundry? [Bluemix]
  • docker-compose with mysql init script
  • ZAP ScriptWriter synch error
  • How to setup dns alias for a service running in Kubernetes
  • Where does Docker know where to pull the .sh scripts from when building a Dockerfile?
  • 4 Solutions collect form web for “Docker container – how to configure so it gets a viable IP address when running in vagrant?”

    The VM generated by vagrant is indeed isolated, in order to access it from your host, you can allocate a private network to it.
    Instead of doing :bridged, try :private_network, ip: "", It should do the trick

    However, this will only allow you to access the VM itself, not the containers.
    In order to do so, when running the container, you can add the -p option

    ex: docker run -d -p 8989 base nc -lkp 8989

    This will run a netcat listening on 8989 within a container and expose the port publicly. As it is also run with -d, the container will be in detached mode and the only output will be the container’s ID

    In order to expose the port, Docker do a simple NAT. In order to know the real port, you can

    do docker port <ID of the container> 8989

    Netcat will be available from the mac at<result>

    I just wrote a tutorial of how to use a host-only network and TCP routing to make this pretty easy. This way you don’t have to map every specific port.

    Important points …

    1) Add host-only network to Virtual Box
    2) Tell the boot2docker VM to have an adapter on the host-only network
    3) Add an IP for the new boot2docker VM host-only networking adapter
    4) Route all Mac OS X traffic for the docker container subnet to that boot2docker VM host-only networking IP

    Actual steps are on the blog with output so you can compare to what you see as you follow them.

    I have installed tomcat from my Dockerfile and forwarded that to 6060 using vagrant`s port forwarding. These are the steps worked for me:

    vagrant provision
    vagrant up
    vagrant ssh
    box_name$ docker run  -i -t -p 8080:8080 bsb_tomcat6 /bin/bash

    Able to see tomcat up & running on localhost:6060, as I have done port forwarding to 6060 in my Vagrantfile

    you also can define PRIVATE_NETWORK and FORWARD_DOCKER_PORTS environment variables to access your services that are running in docker containers:

    $ vagrant halt
    $ export PRIVATE_NETWORK=
    $ vagrant up

    In my case i can access postgres from Mac using

    $ telnet 49154

    to find out actual application port you can use

    $ sudo docker port 1854499c6547 5432
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.