Direct access to containers using Boot2Docker

As part of using Docker as a development tool, I want direct access to docker containers that Boot2Docker has brought up.

For example if

  • Backup stateful docker volume
  • Can not exit from node app, when using docker
  • Send logs to ELK container from Docker containers (without Filebeat)
  • Set write permission into the volume folder inside docker windows/windows container
  • Service 'odoo' failed to build from docker
  • Hashes in `docker pull wordpress`
  • docker inspect {container id}

    says the ip is 172.17.0.5, I would like to be able to connect to the container via that ip address.

    I’m completely against mounting ports on the boot2docker vm and connecting via them, it wont work for me long term.

    Is there any kind of virtualbox config I can change to allow that kind of direct access.

  • How do I push and pull from docker hub in Jenkins declarative pipeline
  • Creating image in Docker fails
  • Cant connect from Node Js (in host) to a MySql container
  • Running gulp in `docker-compose build`
  • Docker Private Registry - push to 'insecure-registry' still complains about 'unknown authority'
  • how can I create a data-container only using docker-compose.yml?
  • One Solution collect form web for “Direct access to containers using Boot2Docker”

    This worked perfectly :
    sudo route -n add 172.17.0.0/16 boot2docker ip

    Found the answer on a comment here :
    http://ispyker.blogspot.co.uk/2014/04/accessing-docker-container-private.html

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