Skip to content
This repository was archived by the owner on Nov 24, 2022. It is now read-only.

Default the lxc__bridge_name to 'vlxcbr1'? #341

Closed
tknerr opened this issue Jan 18, 2015 · 2 comments
Closed

Default the lxc__bridge_name to 'vlxcbr1'? #341

tknerr opened this issue Jan 18, 2015 · 2 comments

Comments

@tknerr
Copy link

tknerr commented Jan 18, 2015

The README says

On its current state, there is a requirement for setting the bridge name that will be created and will allow your machine to comunicate with the container

Which is true, you have to specify lxc__bridge_name: 'vlxcbr1' if you want private networking with the lxc provider to work. It sounds like this would be improved in a future release.

For a short term / quick win improvement, would it make sense to simply default the lxc__bridge_name to 'vlxcbr1'?

That way you don't have to modify each private_network configuration across Vagrantfiles.

@tknerr
Copy link
Author

tknerr commented Jan 18, 2015

P.S.: it seems that you can safely add lxc__bridge_name to existing private_network configurations without affecting other providers. At least for virtualbox it was not a problem.

See here:
tknerr/sample-infrastructure-repo@fbcf0bf#diff-23b6f443c01ea2efcb4f36eedfea9089R25

@fgrehm
Copy link
Owner

fgrehm commented Mar 3, 2015

Eventually we might see some "automagical bridge creation" in place, making the lxc__bridge_name completely optional, but it's not on my short term plans. If someone is up for putting a PR with that I'll consider bringing it in for next release on 1.x series :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants