This is our last status update before we break for the holidays.
On the LXD side of things, this past week saw the inclusion of a couple of minor features (
--all flag and
boot.stop.priority option) and quite a few bugfixes.
In low level LXC, a lot of changes have been going on to improve handling of application containers, including namespace sharing, improved hook handling, improved CRIU integration and new configuration keys to configure container sysctl keys and the out of memory killer.
LXD 2.21 is schedule to be tagged tomorrow and we expect it to roll-out to most users before the end of year. This should be a pretty exciting release!
We’d also like to remind our PPA users that they need to switch to the LXD snap or to one of the in-archive LXD backports as we’ll be removing the LXD PPAs at the end of the year.
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.
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.
--alloption to the
--share-NSset of options to
lxc.hook.versionkey to control hook argument behavior.
relativemount option for relative source paths.
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 offers all the training, software infrastructure, tools, services and support you need for your public and private clouds.
Introduction The focus for this week was on CEPH and LXD clustering, trying to get the last few remaining pieces to work together properly. We’ve tagged a couple more betas as we went through that. We’ve also spent a good chunk of time…
Introduction This past week the LXD team was meeting in Budapest, Hungary. We spent most of our times working on a number of issues targeted at the final 3.0 releases. @freeekanayaka worked with @stgraber to track down an fix a testing…
This article originally appeared on Chris Sanders’ blog MAAS is designed to run in a data center where it expects to have control of DNS and DHCP. The use of an external DHCP server is listed as ‘may work but not supported’ in the…