multiple private networks issue

[jeanfabrice]

Hi

Defining multiple 'private_network' entry in Vagrantfile, does not "work as expected" (i.e works as it does using the virtualbox provider)

Here is network part of my setup :

(1..2).each do |i|
  config.vm.define "n#{i}" do |node|
    node.vm.network "private_network", :adapter=>2, ip: "192.168.1.#{i}",virtualbox__intnet: "cluster", lxc__bridge_name:'cluster'
    node.vm.network "private_network", :adapter=>3, ip: "192.168.0.#{i}",virtualbox__intnet: "private", lxc__bridge_name:'private'
end

Bringing up n1 with lxc provider :

• does not throw any error
• create both eth1and clusterbridge
• does not create eth2
• does not create private bridge

Next, bringing up n2with lxc provider :

• throw an error and halt at the pipework stage while creating the second interface
• does not create eth2
• do create private bridge

Despite the strange behaviour (where, using the same configuration, the second container start throw an error while the first one not), do you confirm that multiple private network is not supported ?

My investigations so far :

• pipework supports a -ioption to specify the interface. When not used, it defaults to eth1
• On the other side, vagrant-lxc does not seem to take care of the ':adapter' parameter from the Vagrantfile. Neither it uses the -ioption of pipework.

Thank you.

[fgrehm]

Oh yeah, I missed out the support for the adapter parameter over here 🐼

[jeanfabrice]

Hi,
here are the Vagrant logs and the Vagrantfile

[fgrehm]

Hey, sorry for the silence here but this project is looking for maintainers 😅

As per #499, I've added the ignored label and will close this issue. Thanks for the interest in the project and LMK if you want to step up and take ownership of this project on that other issue 👋