LXD: Weekly status #11

This article is more than 8 years old.


Introduction

This week has been pretty busy, with the most time consuming work being:

  • More preparation for the upcoming LXC 2.1 release (getting very close now).
  • Dealing with a massive (500+) backlog of patches for the LXC 1.0 and 2.0 stable branches.
  • Quite a bit of refactoring in LXD around the daemon struct and database code.
  • Initial work on performance testing for LXD.
  • Implementation of delta downloads for the daily LXD images.

LXD 2.17 is scheduled to be released on Tuesday and if all goes according to plan, this should be the first release of LXD where the snap package is effectively on par with the Debian package!

We’ve seen quite a big uptake of LXD on a number of Linux distributions thanks to the snap package and are very much looking forward to having the snap package be production ready.

Upcoming conferences

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.

LXD

LXC

LXCFS

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

Ubuntu

  • LXC was updated in the Ubuntu development release to workaround a gcc7 regression.

Snap

  • Updated the wrapper scripts with before comments
  • Cleaned up some of the content filters
  • Added support for bash completion
  • Added support for auto-creation of the “lxd” group
  • Bumped the Go version to 1.8.3
  • Fixed an upgrade issue with snapd 2.27

Talk to us today

Interested in running Ubuntu in your organisation?

Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

By submitting this form, I confirm that I have read and agree to Canonical's Privacy Policy.

Related posts

Hot code burns: the supply chain case for letting your containers cool before you ship

Zero CVEs doesn’t mean secure. It means unexamined. New code has zero CVEs because no one has studied it yet, and if you’re rebuilding nightly from upstream,...

Canonical joins the Rust Foundation as a Gold Member

Canonical’s Gold-level investment in the Rust Foundation supports the long-term health of the Rust programming language and highlights its growing role in...

Canonical partners with Snyk for scanning chiseled Ubuntu containers

Canonical, the publisher of Ubuntu, is pleased to announce a new partnership with developer-focused cybersecurity company Snyk. Snyk Container, Snyk’s...