Can't finish to configure and enable network interfaces when use both public network and docker #7458
Comments
yukihiko-shinoda
changed the title
|
I just tried to reproduce this issue and I am unable to do so using the bento/centos-6.7: Vagrant.configure(2) do |config|
config.vm.box = "bento/centos-6.7"
config.vm.network "public_network"
config.vm.provision "docker"
endoutput: Can you please make sure you have the latest version of that centos box? I know there were some issues early on with guest additions for that particular box, but they have since been fixed. |
|
Hi, @sethvargo, Thank you for your reply. First time "vagrant up" was succeed. Debug outputhttps://gist.github.com/yukihiko-shinoda/9e7f28efa1102089b9b20b1e429821ee |
|
I found. Vagrant was updating eth0 setting. Cause is that network bridge "docker0" is created when docker is installed. But vagrant can't detect "docker0" At first time of "vagrant up", "Configuring and enabling network interfaces..." task run before docker install. |
|
I had same problem with Docker when "vagrant halt && vagrant up":
|
|
I've also hit a similar error, but rather than a halted CentOS guest with Docker installed, I am using a bento/centos6.8 (hand-built using packer) box that I installed Docker on and re-packaged, since provisioning Docker takes quite awhile and I thought it would be a good step to not repeat, since I destroy running instances between usages (instead of halting). I see the same issue and log output as described by @yukihiko-shinoda. To confirm it is the same problem, I went back to using the base bento/centos6.8 (packer-built) without Docker already provisioned, and was able to get past the hung step of "Configuring and enabling network interfaces...". |
|
For me, the workaround was to create a new base box with Docker installed, but disabled on startup, and the sudo yum install bridge-utils -y # needed to use the brctl command below
sudo chkconfig docker off # disable docker on startup
sudo service docker stop # stop docker service
sudo ifconfig docker0 down # turn off docker0 interface
sudo brctl delbr docker0 # delete docker0 bridgeFrom here, I cut a package of the box. Then, as a script command in my config.vm.provision "shell", inline: "sudo service docker start"Starting the Docker service recreates the This won't help with the issue of |
|
any news on this one ?
|
|
I can confirm this issue with:
Linux, and Windows host are fine. |
|
Checking if #7848 might resolve this. |
|
I am having this issue as well with:
The second time I run 'vagrant up', vagrant gets stuck at 'Configuring and enabling network interfaces' for perhaps a minute. After that, it appears to proceed normally and I am able to log into the guest. I don't recall experiencing this issue with Vagrant 1.8.5. |
|
Fixed by: #7866 |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vagrant version
$ vagrant -v
Vagrant 1.8.4
Host operating system
Windows 10 Pro x64
Guest operating system
CentOS6.7(image: bento v.2.2.7)
https://atlas.hashicorp.com/bento/boxes/centos-6.7
Vagrantfile
Debug output
https://gist.github.com/yukihiko-shinoda/4d4731a595f8af6982f2b8ef5849dd09
Expected behavior
Successfully vagrant up.
Actual behavior
Can't finish to Configure and enable network interfaces.
Steps to reproduce
1.Prepare Vagrantfile which use both config.vm.network "public_network" and config.vm.provision "docker"
2.vagrant up
3.vagrant halt && vagrant up
The text was updated successfully, but these errors were encountered: