try running vagrant up with --debug, this can shed some light on what's
going on.
On Wednesday, May 14, 2014 5:20:35 PM UTC+3, Paul Umbers wrote:
>
> Running Windows 7 Pro SP1 host, Vagrant 1.6.2 and VirtualBox 4.3.10
> r93012. When I start a docker container using "vagrant up
> --provider=docker" with the following Vagrantfile:
>
> Vagrant.configure("2") do |config|
> config.vm.provider "docker" do |docker|
> docker.image = "dockerfile/mongodb"
> docker.has_ssh = true
> end
> end
>
> ... the first part of the startup seems normal, but then hangs
> indefinitely on "Syncing folders to the host VM ...":
>
> Bringing machine 'default' up with 'docker' provider...
> ==> default: Docker host is required. One will be created if necessary...
> default: Vagrant will now create or start a local VM to act as the
> Docker
> default: host. You'll see the output of the `vagrant up` for this VM
> below.
> default:
> default: Importing base box 'mitchellh/boot2docker'...
> default: Matching MAC address for NAT networking...
> default: Checking if box 'mitchellh/boot2docker' is up to date...
> default: Setting the name of the VM:
> docker-host_default_1400076651055_74297
> default: Clearing any previously set network interfaces...
> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Forwarding ports...
> default: 4243 => 4243 (adapter 1)
> 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: docker
> default: SSH auth method: private key
> default: Warning: Connection timeout. Retrying...
> default: Machine booted and ready!
> ==> default: Syncing folders to the host VM...
>
> This happens whether I use a canned Docker image (as above) or point the
> Vagrantfile at a Dockerfile for Docker to build the image. Disabling folder
> sync appears to let the boot continue normally, but I need to have some
> additional files pulled in to the image from the host file system, so
> really need folder syncing to work.
>
> I've not been able to find anything definitive using Google, or in this
> forum or on the Vagrant issues list. I did find this:
> https://github.com/mitchellh/vagrant/issues/3789 which relates to an
> rsync installation failure, but again: not definitive. I'm wondering if
> there is an authentication problem and Vagrant can't log in to the VM,
> would that cause it to hang at this point?
>
> Anybody got any ideas?
>
> Thx.
>
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
