search

julien-duponchelle / docker-osx

Fast and easy installation of Docker on OS X
1.03k stars 70 forks source link

Unable to connect #62

Open petergarbers opened 10 years ago

petergarbers commented 10 years ago

Hi there,

This is with a fresh install of vagrant and virtual box and using the default docker-osx settings and environment variables. Any assistance as to where I'm going wrong would be greatly appreciated.

~ docker-osx shell Starting local Docker environment... /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.3/lib/vagrant/pre-rubygems.rb:31: warning: Insecure world writable dir /usr/local in PATH, mode 040777 /Applications/Vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/runtime.rb:222: warning: Insecure world writable dir /usr/local in PATH, mode 040777 Start Docker Virtual machine /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.3/lib/vagrant/pre-rubygems.rb:31: warning: Insecure world writable dir /usr/local in PATH, mode 040777 /Applications/Vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/runtime.rb:222: warning: Insecure world writable dir /usr/local in PATH, mode 040777 Bringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 => 2222 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. 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.

cscade commented 10 years ago

This isn't a docker-osx issue. I have the same problem occasionally with multiple vagrant VMs on my older 2008 macbook pro. A restart has always resolved the issue for me.

petergarbers commented 10 years ago

@cscade Thanks for the reply. I've restarted several times after installing to no avail.

jayd3e commented 10 years ago

Seeing this too now for some reason.... Has never happened before to me.

kzinizk commented 10 years ago

me too

Workman commented 10 years ago

docker.io has now changed to docker.com. Update as necessary.

tmrudick commented 10 years ago

I had the same issue with a clean install. I ended up running the machine manually from VirtualBox and saw that the machine was hanging up on a GRUB menu to select the operating system to boot. Made a selection, shut down the VM and then docker-osx shell worked fine for subsequent runs.