Skip to content

Instantly share code, notes, and snippets.

@cronnelly

cronnelly/gist:98345100afe21840267270da3283b371

Created April 5, 2016 18:00
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save cronnelly/98345100afe21840267270da3283b371 to your computer and use it in GitHub Desktop.
Save cronnelly/98345100afe21840267270da3283b371 to your computer and use it in GitHub Desktop.
Download ZIP
lxcbr0 is being replaced by lxdbr0
Raw
gistfile1.txt
┌─────────────────────────────────────────────────────────┤ Configuring lxd ├──────────────────────────────────────────────────────────┐
│ │
│ lxcbr0 is being replaced by lxdbr0 │
│ │
│ With this package upgrade LXD is moving away from the LXC provided lxcbr0 bridge and moving to its own lxdbr0 bridge. │
│ │
│ The reason for this switch is: │
│ - Drop the dependency on the old LXC (lxc1) package. │
│ - Only run the bridge when LXD is running. │
│ - Don't hardcode a subnet which may be used by the user. │
│ │
│ │
│ Important differences between lxcbr0 and lxdbr0: │
│ - The lxdbr0 bridge DOES NOT come with ANY configured IPv4 or IPv6 subnet. │
│ - The bridge provides basic HTTP connectivity out of the box by way of │
│ a tiny HTTP PROXY server running on an IPv6 link-local address. │
│ - The user IS EXPECTED to configure the bridge to use an UNUSED subnet │
│ on their network. │
│ │
│ │
│ To configure lxdbr0 to your liking, please run: dpkg-reconfigure lxd │
│ │
│ To stay on the old lxcbr0 bridge, make sure you have the "lxc1" package installed, then select the "use an existing bridge" option. │
│ │
│ <Ok> │
│ │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment