Weekly status #45

Weekly status for the week of the 23th to the 29th of April 2018.


Our focus this past week has very much been bugfixing, trying to be very reactive on all bug reports around LXD 3.0 and then pushing those fixes to our users through the LXD snap.

This past week also saw the release of Ubuntu 18.04 LTS which ships with LXD 3.0 pre-installed in its server image!

We’ve also finally started migrating some of our images over to distrobuilder. The main integration work in our signing and publishing infrastructure has now been done and the Debian images are now generated using distrobuilder on Jenkins and published through the usual set of servers. We expect more distributions to follow soon!

On the feature development side of things, most of our efforts are going into the backup/restore feature which has been updated a bit after an initial review and that will ship with LXD 3.1.

Upcoming conferences and events

Ongoing projects

The list below is feature or refactoring work which will span several weeks/months and can’t be tied directly to a single Github issue or pull request.

Upstream changes

The items listed below are highlights of the work which happened upstream over the past week and which will be included in the next release.




  • Nothing to report this week


  • Fixed paths in exclusion list
  • Fixed filename of unprivileged LXC config

Distribution work

This section is used to track the work done in downstream Linux distributions to ship the latest LXC, LXD and LXCFS as well as work to get various software to work properly inside containers.


  • Ubuntu 18.04 released with LXD 3.0


  • Cherry-picked a large quantity of LXD 3.0 bugfixes

Tweaked lxd init to offer using a Fan bridge when running clustered LXD2

Above the last item on the list of items for lxd.
Please - - - what does this mean?

How does this differ from lxdbr0 or macvlan?

The Ubuntu Fan is a dynamic, stateless overlay network which lets you have a bridge per host on your network and have routes automatically generated between the nodes so that they can reach each another.

Thank you for your response! So how is ‘fan’ different from lxdbr0?

lxdbr0 is local to your machine, if you have a lxdbr0 on two systems, the containers on the first cannot talk to the containers on the second.