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

  • Installing libLAS on docker python - No such file or directory
  • Scaling Node instances inside of Docker containers
  • Need floating IPs to create a container in IBM Bluemix (BXNUI0110E)
  • How to enable SSL in docker with nginx hosted in Ubuntu
  • Cannot connect Docker container to Weave network
  • One docker container per node or many containers per big node
  • 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 ?

  • Connecting zeppelin docker with hive
  • How can i mount volume of glusterfs to /var/lib/docker in ubuntu 14.04
  • how can I support http_proxy or logic control in Dockerfile during docker build?
  • Amazon ECS error: cannot create a task definition with no containers
  • gitlab CI build runs on my local docker container
  • Docker ELK 5.4.0 - Kibana did not load properly. Check the server output for more information
  • 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.