Weekly status #107

Weekly status for the weeks of the 15th to the 21st of July.


This past week has mostly been a maintenance week with bug fixes, code re-organizations for our larger projects, and other small improvements.

LXD 3.15 started rolling out to our stable users halfway through the week.

Several cluster heartbeat related bugs since the LXD 3.15 release have been fixed, with the aim of reducing the time it takes for cluster membership changes to be applied throughout the cluster nodes.

A number of regressions/bugs in the new dqlite 1.0 backend used by LXD 3.15 were also tracked down, resolved and rolled out to affected users.

The ability to create an empty container has been added to LXD, which is useful if you already have a rootfs you want to use for a container.

On the LXCFS side, several improvements to the way CPU usage is accounted for have been added.

The LXC 3.2 and LXCFS 3.1 releases got delayed a bit and are now expected for early this week.

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.

  • Rework of internal LXD device handling
  • Rework of internal LXD storage handling
  • Ubuntu Core 18 support in distrobuilder
  • Cloud-init for all distrobuilder images
  • Various kernel work
  • 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

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


  • Fixed a long standing bug where lxcfs incorrect inherited the LXD socket
  • Did several round of cherry-pick of fixes on top of LXD 3.15
  • Added the ethertypes and protocols files required for the new ipv4/ipv6 filtering feature

Is there any documentation about it?


lxc init now has a --empty option you can pass which will create an empty container.

Moving stuff into it would still involve you mounting its filesystem and transferring data manually though, or you could use lxd-p2c which does effectively that for you over the migration API.

Is there ready migration script from OpenVZ 6?

I wrote bash script for this, but have to set all settings like cpu numbers and memory limit manually now. Is there a better way?

I’ve not heard anyone having such a script, you may want to publish yours so that others can make use of it.

lxd-p2c certainly can work for the data migration bits but having something convert the configuration sounds useful.