Hi all,
we are using Vagrant on Windows with Docker as provider and a custom
Docker host (ubuntu/trusty64) set up with the Docker provisioner.
Our Docker containers have SSH enabled.
The VM looks like this:
config.vm.define "test", primary: true do |test|
test.vm.provider "docker" do |d|
d.image = "internal-registry:5010/test/sample"
d.vagrant_vagrantfile = "../docker-host/Vagrantfile"
d.has_ssh=true
end
end
We frequently have issues where Vagrant is stuck in "Waiting for machine
to boot", although the container is up (I can log into the Docker
container with SSH as well as into the Docker host). Sometimes this
happens multiple times in a row and then for hours or even days without
it happening once. Also it happens more frequently on some machines than
on others, yet I haven't been able to figure out the difference or what
causes this. Maybe some minor differences in the involved network hardware?
We're on Vagrant 1.7.2 and have VirtualBox versions 4.3.22 and 4.3.26,
OS is Win7 Pro 64bit.
When the issue occurs, Vagrant with --debug keeps printing
DEBUG ssh: Sending SSH keep-alive...
to the console until the boot timeout occurs.
Does anyone have any idea what this could be? Or how to further debug this?
Greetings
-Sascha-
--
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.
