-
Notifications
You must be signed in to change notification settings - Fork 181
vagrant halt removes lxc bridge that leads to impossibility to vagrant up afterwards #353
Comments
|
@fgrehm do you have an example for how to configure Vagrantfile for creating new bridge for every vagrant up ? |
Things should work just fine if you use other bridge name. Here's more information on how it works: https://github.com/fgrehm/vagrant-lxc#private-networks-experimental If that is not clear enough please LMK so we can discuss how to improve docs! |
Ugh I meant to add a check around this myself. I was hackily avoiding the issue by leaving other containers attached to the bridge. I think it would be reasonable to avoid deleting lxcbr0, docker0, and virbr0 (all common default bridge names). |
I think the reason this is not obvious because I have to set the bridge name manually, and that makes me expect to be able to use a preconfigured bridge. The virtualbox driver just uses the first matching vboxnet right? ( Btw, looking at the virtualbox driver, it looks like it optionally uses |
Just out of curiosity, why are you guys using private networking with
The reason I did not do that is because I have some plans to spike on getting vagrant-lxc to create a bridge that looks like Ubuntu's
Sorry but I think it is clear from the readme how it works: "Once the last vagrant-lxc container attached to the bridge gets vagrant halted, the plugin will delete the bridge." (not to say that the functionality is experimental 😄 )
Automagic bridge naming is going to be supported eventually. Private networking is a feature I do not use that much and I wanted to first validate that the basic "infrastructure" (aka |
Perhaps adding support for |
Fixing fgrehm#353 issue
Fixing fgrehm#353 issue
Fixing fgrehm#353 issue
Fixing fgrehm#353 issue
Fixing fgrehm#353 issue
Fixed in master |
Here is a working config
lxcbr0
being enabled during system startupwhen running
vagrant halt
there is a messageSo vagrant up won't work before system restart and recreate lxc bridge
I see no ability to restart lxc bridge, because it is started via runlevel during system boot
Are there any config for skippping bridge removal for vagrant halt?
If no, we totally need it, because it leads to unusable behaviour
The text was updated successfully, but these errors were encountered: