Weekly status #64

Weekly status for the week of the 3rd to the 9th of September.


Another pretty quiet week for the LXD team as half the team was traveling.

The focus for this week has been on finalizing a number of features for the upcoming LXD 3.5 release as well as continuing the work on LXD projects.

On top of that feature work, the snap packages got refreshed and a number of bugs in LXC and LXD got fixed.

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


  • Nothing to report this week

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.


  • Uploaded LXC 3.0.2 to bionic-proposed
  • Uploaded LXCFS 3.0.2 to bionic-proposed
  • Uploaded LXD 3.0.2 to bionic-proposed


  • Added an install hook to pre-create some paths
  • Preparing for socket activation in lxd.migrate
  • Tweaked startup script to make sure all paths exist
  • Updated lxd.migrate to recommend removing packages
  • Cherry-picked a large set of bugfixes on top of LXD 3.4
  • Updated to Go 1.11
  • Updated to ZFS 0.7.10
  • Added cluster refresh logic to auto-trigger refreshes

Still not seeing the updated packages in the proposed repo or on launchpad.

That’s because all 3 packages are in the review queue waiting for someone on the stable release update team to review and let them into -proposed. Sadly not much we can do at that stage but wait and see.

That’s unfortunate, you’d think they’d be higher priority with the CVE fixes

The CVE has been fixed in Ubuntu for weeks already. Ubuntu pushed a patched version of LXC at the exact time the CVE was made public, so the updates we’re pushing now are just bugfixes, no security content.