Docker and Windows – Problems with SSH on default container

i’m new to Docker and i’ve just intalled Docker ToolBox 1.11.1 on my Windows 7 (64 bit).
When running Quickstart Terminal i’ve got problems with creating default container.
After reading a bunch of forums i’ve invoked :

docker-machine rm -f default
docker-machine --debug create -d virtualbox default 

But still without result. Full logs from last operation are :
https://gist.github.com/anonymous/117e302c047492170a6f0c7d4e79199a

  • Docker - Running Postgres Scripts inside Container
  • Elasticsearch won't run with Docker
  • How to aggregate logs for all docker containers in mesos
  • How to create a virtual cluster using docker on a single node?
  • reconfigure timezone inside docker not working
  • akka cluster nodes behind NAT (using docker)
  • They end up with phrase :
    “(default) DBG | Error dialing TCP: dial tcp 127.0.0.1:49659: connectex: No connection could be made because the target machine actively refused it.”

    I’ve have no idea how to fix that. Can someone help me ?

  • Console App or Windows Service in Windows Container?
  • Docker (compose) and socket io - how to link containers
  • Developing in a Docker image that's under version control
  • Redis memory usage, ZSET and docker
  • Docker Compose volume doesn't persist files in subfolders
  • Issue with Jenkins pipeline script and docker maven image
  • One Solution collect form web for “Docker and Windows – Problems with SSH on default container”

    In windows and Mac OS Docker run in a virtual machine. When you install Docker using the Docker Toolbox, it takes care of install Virtual Box, create a “default” virtual machine and configure it to run a Boot2Docker image.
    With the command:

    docker-machine rm -f default
    

    you are removing this default VM. Then running the command:

    docker-machine --debug create -d virtualbox default
    

    you are creating a new VM called “default”, so you are not creating or starting any default windows container.

    “Actively refused it” means that the host sent a reset instead of an ack when you tried to connect. Please, check the firewall or the proxy configuration because this is a communication problem.
    Hope this can help.

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