Open lpsguilloul opened 4 years ago
Hey there, thanks for the bug report!
From this line the debug log
ERROR vagrant: #<Vagrant::Errors::ProviderNotUsable: The provider 'docker' that was requested to back the machine 'jenkins' is reporting that it isn't usable on this system. The reason is shown below:
It seems like docker is being executed on the host machine, not the dockerhost
machine. This happens because Vagrant is checking that docker is usable on the host. This check makes sense when trying to use the docker provider on the host system. However, perhaps it is not needed when executing docker remotely. So, this is a bug with the docker provider usability check.
As a workaround for this issue, you can install docker.
I even tried the simplest vagrant configuration to be able to use docker provider but nothing worked.
In order use the docker provider, docker must be installed on the host machine.
Vagrant version
Vagrant 2.2.9
Host operating system
Windows 10 x64
Guest operating system
centos/7
Vagrantfile
I use two files : Vagrantfile and Host_Vagrantfile
Vagrantfile
Host_Vagrantfile
Debug output
https://gist.github.com/lpsguilloul/7baf85c37d184b7930f44ce97862f0e4
Expected behavior
I'm using docker provider. When vagrant up is executed, vagrant should spin up the VM host and install Docker before executing any docker commands to set up the containers.
Actual behavior
Vagrant doesn't spin up the VM host. It's as if, it's ignoring the vagrant_vagrantfile setting passed to the docker provider.
When I remove "ENV['VAGRANT_DEFAULT_PROVIDER'] = 'docker'" and execute vagrant up, I get another error :
Reinstalling Vagrant as suggested in this feed doesn't work. I was able to reproduce the same behavior with Vagrant 2.2.8.
I even tried the simplest vagrant configuration to be able to use docker provider but nothing worked.
On the contrary, docker provision works perfectly.
Steps to reproduce
Thanks for your help.
Best regards, Lourdes