Weekly status #282

Weekly status for the week of 16th January to 22nd January.


A bumper week of releases! The highlight of the past week was the release of LXD 5.0.2 LTS, LXC 5.0.2 LTS and LXCFS 5.0.3 LTS. These are the latest in their respective 5.0 LTS series (which are supported until June 2027). Please see their release notes for more details.

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)



  • Added cluster member state lxc cluster show <instance> command and associated API endpoint. This command shows sysinfo and storage pool usage information for the specified cluster member.
  • Further reductions to the number of DB transactions started in common operations.
  • Improved live migration error messages.

Bug fixes:

  • Fixed a regression in LXD 5.10 that prevented profiles being included when copying an instance (if not specified in the request itself). This didn’t affect lxc copy, but only affected direct API requests that didn’t explicitly include the profiles.
  • Fixed some edge cases in the container shutdown/stop process to make it more resilient.
  • Fixed MIPS architecture aliases.
  • Fixed dnsmasq version detection to work in environments that have the LANGUAGE variable set (by forcing english language when invoking dnsmasq version check).


Bug fixes:

  • Fixed deadlock regression.
  • Fixed newline in jinja2 renderer.



  • Ensure error messages are logged in main.
  • Added support for next Funtoo release.

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

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



LXD Charm

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


  • lxd: Cherry-pick upstream bugfixes
  • Updated 5.0 branch to line up with latest
1 Like

Does the database transaction reduction mean it could be viable to run a cluster in a cross data center environment?

Still not something we’d generally recommend, but those reductions certainly would make such a setup less painful.

So clustering should only be used if machines are in the same data center?

Yes, or low latency links.

So for clustering is it built in mind for identical systems in the same location or is it ok for the systems to be different?

As all the database queries go to the leader member, if there is a lot of latency between it and the other members it can become intolerably slow.

But you can have mixed clusters of different machines. Although they need to some the similar connectivity and storage as LXD networks and storage pools must exist on every member.