Weekly status #301

Weekly status for the week of 29th May to 4th June.


This past week has primarily been focused on getting the issue count down with a variety of improvements and bug fixes.

Job openings

Canonical Ltd. strengthens its investment into LXD and is looking at building multiple squads under the technical leadership of @stgraber.

As such, we are looking for first line managers (highly technical) and individual contributors to grow the team and pursue our efforts around scalability and clustering.

All positions are 100% remote with some travel for internal events and conferences.

For more info please see LXD related openings at Canonical Ltd (2022-2023)



  • Allowed hot-plugging of ovn NICs into VMs.
  • Switched the order of image deletion and creation for lxc publish --reuse command. The order is now: create image, delete image if necessary, finally add/remove any aliases.
  • Any left over operations for the local LXD server are cleared on start up.

Bug fixes:

  • Fixed bug that meant instances that were previously running were not restarted during cluster instance healing evacuation.
  • lxc init and lxc launch now accept the Description field from stdin.
  • Fixed bug in lxd recover that meant that database records created were not all removed when an error occurred.
  • Fixed bug where loop backed files created were not removed if an error occurred during storage pool creation.
  • LXD now handles more statuses from QEMU so that VMs do not end up in a STOPPED state if the the QEMU process is still running. If the QEMU process is not in a recognized state then it will show as ERROR allowing a forced stop with lxc stop -f.
  • Fixed some inconsistencies in the resource URLs for instance snapshot operation responses.
  • Fixed potential race condition during VM migration that could cause incorrect failure due to context cancellation on disconnect at end of migration.
  • Fixed zfs list -r recommendation in ZFS storage pool create when a non-empty pool is found.

YouTube videos

The LXD team is running a YouTube channel with live streams covering LXD releases and weekly videos on different aspects of LXD. You may want to give it a watch and/or subscribe for more content in the coming weeks.


Contribute to LXD

Ever wanted to contribute to LXD but not sure where to start?
We’ve recently gone through some effort to properly tag issues suitable for new contributors on Github: Easy issues for new contributors

Upcoming events

  • Nothing to report this week

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.

  • Stable release work for LXC, LXCFS and LXD

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


  • Nothing to report this week

LXD Charm

  • 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.


  • Nothing to report this week


  • Nothing to report this week