Skip to content

Instantly share code, notes, and snippets.

@lbjay
Created November 26, 2014 20:38
Show Gist options
  • Save lbjay/343aee36b7ecdcbe4c6d to your computer and use it in GitHub Desktop.
Save lbjay/343aee36b7ecdcbe4c6d to your computer and use it in GitHub Desktop.
Bringing machine 'default' up with 'docker' provider...
==> default: Building the container from a Dockerfile...
default: Image: e7c5e7043c84
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Creating the container...
default: Name: vagrant_elastic_docker_default_1417033411
default: Image: e7c5e7043c84
default: Volume: /home/jluker/projects/vagrant_elastic_docker:/vagrant
default: Port: 2200:22
default:
default: Container created: 01b7b6621133f75a
==> default: Starting container...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 172.17.0.250:22
default: SSH username: root
default: SSH auth method: private key
default: Warning: Connection refused. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment