--- title: Blog posts tagged "machine containers" description: Canonical makes open source secure, reliable and easy to use, providing support for Ubuntu and a portfolio of enterprise-grade technologies. Founded in 2004, Canonical operates globally with team members in over 80 countries. url: https://canonical.com/blog/tag/machine-containers --- # Blog posts tagged "machine containers" #### [Kubernetes on a single machine](https://canonical.com/blog/kubernetes-on-a-single-machine) As developers, we do not always have access to a production-like environment to test new features and run proof-of-concepts. This is why it can be very interesting to deploy Kubernetes on a single machine. Of course, there is the new microk8s snap that allows a super fast deployment of a k8s cluster on a laptop --- Cloud and server #### [LXD Clusters: A Primer](https://canonical.com/blog/lxd-clusters-a-primer) Since its inception, LXD has been striving to offer a fresh and intuitive user experience for machine containers. LXD instances can be managed over the network through a REST API and a single command line tool. For large scale LXD deployments, OpenStack has been the standard approach: using Nova LXD, lightweight containers replace traditi --- Cloud and server #### [LXD weekly status #43](https://canonical.com/blog/lxd-weekly-status-43) Introduction This week’s focus was on bugfixes with a good number of clustering related fixes and improvements as well as some tweaks and fixes to other recently added features. On the feature development front, the current focus is on improving the database tooling in LXD and adding a new backup feature to the API to --- Cloud and server #### [On the road to lean infrastructure](https://canonical.com/blog/on-the-road-to-lean-infrastructure) On April 24 2008, Ubuntu 8.04 LTS Hardy Heron was released. That was a decade ago, when the modern cloud computing era was dawning: Amazon’s EC2 was still in beta, Google had just released the Google App Engine and the word “container” was dominating the plastics industry rather than IT. A lot has changed since --- Cloud and server #### [LXD weekly status #42](https://canonical.com/blog/lxd-weekly-status-42) Introduction As this was the week following our major 3.0 release, we’ve been very actively working on early bug reports and sorting out packaging for this in the distros. This led to quite a number of bugfixes being done, issues investigated and a large number of updates to our snap and Debian packages for the --- Cloud and server #### [LXD weekly status #41](https://canonical.com/blog/lxd-weekly-status-41) Introduction The highlight for this week is the release of LXD, LXC and LXCFS 3.0! Those 3 releases are LTS releases and will be supported for the next 5 years. The relevant release announcements can be found here: LXD 3.0 LXC 3.0 LXCFS 3.0 We’d like to thank every one of our contributors who made --- Cloud and server #### [LXD weekly status #40](https://canonical.com/blog/lxd-weekly-status-40) Introduction This week we released another LXD beta and two LXC betas. We also made good progress replacing the command line parser in LXD, finishing the port of the lxd command line tool with only lxc left to port at this point. Remote copy and move of storage volume was completed and merged in LXD, --- Cloud and server #### [LXD weekly status #39](https://canonical.com/blog/lxd-weekly-status-39) 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 getting Ubuntu and Debian images to switch over to distrobuilder. They’re now --- Cloud and server #### [LXD weekly status #38](https://canonical.com/blog/lxd-weekly-status-38) 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 regression on s390x, then worked on CEPH support in LXD clustering as well as --- Cloud and server #### [LXD weekly status #37](https://canonical.com/blog/lxd-weekly-status-37) Introduction So this past week was rather intense, in a nutshell, we’ve: Merged LXD clustering support Split python3-lxc, lua-lxc and lxc-templates out of the LXC codebase Moved libpam-cgfs from lxcfs to lxc Released 3.0.0 beta1 of python3-lxc and lxc-templates Released 3.0.0 beta1 of lxcfs Released 3.0.0 beta1 of lxc Released 3.0.0 beta1 --- Cloud and server #### [LXD weekly status #36](https://canonical.com/blog/lxd-weekly-status-36) Introduction This past week we’ve been working very hard to land all those last few bits ahead of us tagging a number of 3.0.0.beta1 releases of all our repositories. We’re now waiting for a few last bits to land, including LXD clustering and some reshuffling of templates, bindings and tools in LXC. The current plan --- Cloud and server #### [LXD Weekly Status #35](https://canonical.com/blog/lxd-weekly-status-35) Introduction This past week we’ve been focusing on a number of open pull requests, getting closer to merging improvements to our storage volume handling, unix char/block devices handling and the massive clustering branch that’s been cooking for a while. We’re hoping to see most of those land at some point this coming week. On the --- Cloud and server #### [LXD weekly status #34](https://canonical.com/blog/lxd-weekly-status-34) Introduction A lot happened this past week. @brauner is making great progress cleaning everything up in liblxc and related projects ahead of the 3.0 release, @freeekanayaka has been sorting out the last few missing bits for LXD clustering and @monstermunchkin has been busy working on our new distrobuilder tool! On top of all that, we’ve --- Cloud and server #### [LXD weekly status #33](https://canonical.com/blog/lxd-weekly-status-33) Weekly status for the week of the 29th of January to the 5th of February 2018. Introduction This past week, the entire LXD team was meeting in Brussels to work together for a few days ahead of FOSDEM. During those days, we’ve been looking into our short and long term plans, worked together on our --- Cloud and server #### [LXD weekly status #32](https://canonical.com/blog/lxd-weekly-status-32) The focus of this week has been preparing for our trip to Brussels where we’ll be spending 3 days all working together on LXD before attending and presenting at FOSDEM. @brauner is making good progress on preparing for the liblxc 3.0 release, moving all the various language bindings and tools out of the main tree --- Cloud and server #### [LXD: five easy pieces](https://canonical.com/blog/lxd-5-easy-pieces) Machine containers, like LXD, proliferate in the datacenters: they provide a native control plane for OpenStack and a lightweight hypervisor for its tenants. LXD optimizes resource allocation and utilization for Kubernetes clusters, modernizes workload management in HPC infrastructure and streamlines lift and shift for legacy applications --- Cloud and server 1. *Previous page* 2. [1](https://canonical.com/blog/tag/machine-containers?format=md&page=1) 3. [2](https://canonical.com/blog/tag/machine-containers?format=md&page=2) 4. [*Next page*](https://canonical.com/blog/tag/machine-containers?format=md&page=2)