Freight forwarders are accelerating digitalization to boost efficiency, but this also increases vulnerability to cyber threats. Ransomware attacks show how even short disruptions can ripple through supply chains, especially impacting small and medium-sized forwarders. FIATA is leading efforts to strengthen cyber resilience through practical guidance, training, and tools for the global freight forwarding community.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Stéphane Graber
Stable Linux mainline builds
Why use a mainline kernel For the past year or so, I’ve increasingly been using mainline Linux kernels on my various servers and eventually laptop and desktop machines too. That was transitioning from Ubuntu’s generic kernel which I feel has sadly decreased in quality over time. The Ubuntu kernel includes a lot of backported fixes and occasionally, those backports go bad, resulting in missing commits, introducing bugs and regressions.
Time to move on | Stéphane Graber's website
Resignation After a bit over 12 years working for Canonical, Friday 7th of July was my last day. It’s a bit of a bittersweet moment leaving a company after you’ve invested so much of your time into it, but I believe that now was the right time for me. As I’ve told colleagues and upper management, Canonical isn’t the company I excitedly joined back in 2011 and it’s not a company that I would want to join today, therefore it shouldn’t be a company that I keep working for either.
Inexpensive highly available LXD cluster: Server setup
The previous post went over the planned redundancy aspect of this setup at the storage, networking and control plane level. Now let’s see how to get those systems installed and configured for this setup. Firmware updates and configuration First thing first, whether its systems coming from an eBay seller or straight from the factory, the first step is always to update all firmware to the latest available.
Inexpensive highly available LXD cluster: Redundancy
In the previous post I went over the reasons for switching to my own hardware and what hardware I ended up selecting for the job. Now it’s time to look at how I intend to achieve the high availability goals of this setup. Effectively limiting the number of single point of failure as much as possible.
Inexpensive highly available LXD cluster: Introduction
It’s been a couple of years since I last posted here, instead I’ve mostly been focusing on LXD specific content which I’ve been publishing on our discussion forum rather than on my personal blog. But this is going to be a bit of a journey and is about my personal infrastructure so this feels like a better home for it! What is this all about?
Using LXD on your Chromebook
Introduction On supported Chromebook, starting with Chrome OS 69, a new feature called Linux Apps was introduced. This allows Chrome OS users, on supported to install normal Linux applications from the Debian repository and have them integrate with the underlying Chrome OS desktop. The feature has evolved quite a bit since its introduction, including recent work on getting sound, USB and even GPU acceleration to those applications.
Using LXD on your Chromebook - Ubuntu Blog
By Stéphane Graber on 26 February 2019 Introduction On supported Chromebook, starting with Chrome OS 69, a new feature called Linux Apps was introduced. This allows Chrome OS users, on supported to install normal Linux applications from the Debian repository and have them integrate with the underlying Chrome OS desktop. The feature has evolved quite a bit since its introduction, including recent work on getting sound, USB and even GPU acceleration to those applications.
Using LXD on your Chromebook
Introduction On supported Chromebook, starting with Chrome OS 69, a new feature called Linux Apps was introduced. This allows Chrome OS users, on supported to install normal Linux applications from the Debian repository and have them integrate with the underlying Chrome OS desktop. The feature has evolved quite a bit since its introduction, including recent work on getting sound, USB and even GPU acceleration to those applications.
lxc-user-nic allows for open() of arbitrary paths
CVE-2018-6556: lxc-user-nic allows for open() of arbitrary paths From: Stéphane Graber Date: Mon, 6 Aug 2018 12:27:03 -0400 Hello, This is a notice for a security issue affecting the following LXC versions: - 2.0.9 and higher - 3.0.0 and higher Description of the issue: lxc-user-nic (setuid) when asked to delete a network interface will unconditionally open a user provided path.
LXD weekly status #44
Another week of bugfixes for us as more and more people update to the 3.0 releases! Quite a bit of work went into improving the handling of the two database in LXD 3.0, making it easier for us to debug issues and provide fixes to our users when something goes wrong. Work is also continuing on the new backup/restore API for LXD with it hopefully landing later this week. We’re also excited to see LXD debuts on the Chromebooks through the new Crostini feature.
LXD weekly status #43
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 implement container export/import. 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.
LXD weekly status #42
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 various components.
LXD weekly status #41
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.
LXD weekly status #40
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 command line tool with only left to port at this point. Remote copy and move of storage volume was completed and merged in LXD, as was the addition of a new event class and a number of improvements to the clustering code.
LXD weekly status #39
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 both building daily on Jenkins and we’re just a few changes to our publication logic away from switching to them by default on the image server.
LXD weekly status #38
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 fixing some DB upgrade issues encountered by some of our beta users.
LXD weekly status #37
So this past week was rather intense, in a nutshell, we’ve: So we’ve finally done it, most of the work that we wanted in for our 3.0 LTS release of all LXC/LXD/LXCFS repositories has been merged and we’re now focused on a few remaining tweaks, small additions and fixes with a plan to release the final 3.0 by the end of the month.
LXD weekly status #36
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 is to start tagging a number of projects later today, tomorrow and Wednesday, with all of them making their way into Ubuntu by end of day on Thursday.
LXD Weekly Status #35
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 LXC side of things, the focus was on bugfixes and cleanups as well as preparing for the removal of the python3 and lua bindings from the main repository.
LXD weekly status #34
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 landed a variety of smaller features in LXD based on past user requests.
LXD weekly status #33
Weekly status for the week of the 29th of January to the 5th of February 2018. 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 upcoming clustering feature, discussed the ongoing work on the new image building tooling and got to debug a number of kernel issues.
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 and into separate repositories.
LXD Weekly Status #31
Nothing too major happened this past week. Part of the time was at an internal planning meeting and the rest have been working on clustering, preparation for 3.0 and fixing a variety of bugs.
LXD Weekly Status #30
The main highlight for this week was the inclusion of the new device in LXD, thanks to the hard work of some University of Texas students! The rest of the time was spent fixing a number of bugs, working on various bits of kernel work, getting the upcoming clustering work to go through our CI process and preparing for a number of planning meetings that are going on this week.
LXD Weekly Status #29
And we’re back from the holidays! This “weekly” summary is covering everything that happened the past 3 weeks. The big highlight was the release of LXD 2.21 on the 19th of December. During the holidays, we merged quite a number of bugfixes and smaller features in LXC and LXD with the bigger feature development only resuming now.
LXD Weekly Status #28
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 ( flag and 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 Weekly Status #27
This past week was incredibly busy and featureful for both LXC and LXD. We landed Infinband support in LXD, alongside new configuration keys to control the presence of /dev/lxd in the container and support for pre-migration of memory during container live-migration. That’s on top of a variety of bugfixes and other still ongoing feature work.
LXD Weekly Status #26
Focus this week has been on infiniband support and more clustering related work with a number of bugfixes, cleanups and refactoring on the side. We’ve been doing some small tweaks and bugfixes on the LXD snap based on user feedback as more and more users are migrating to it. We’re also getting ready to push LXD 2.0.11 to a lot of our users, fixing a lot of bugs in the process and bringing some small usability tweaks too.
LXD Weekly Status #25
This week has been split between some upcoming feature work (infiniband and clustering), helping some new contributors get started with contributing to LXD and doing a lot of backports to the stable branches. Our stable branch backlog is now empty on all 3 projects and @brauner is now handling this for LXC with @stgraber handling the stable branches of LXD and LXCFS.
LXD Weekly Status #24
The highlight of this week was the release of LXD 2.20 which introduces a number of exciting new features. LXD 2.20 should now be available everywhere through both native packages and snap. We also started the process of deprecating the various LXD PPAs, see below for details. Our next milestone is LXD 2.21 in about a month which will be the last LXD release of the year and the last LXD 2.x release. Once 2.21 is out, we’ll focus on LXD 3.0 with the first alpha expected in January.
LXD Weekly Status #23
The main focus this past week has been on merging a pretty large refactoring branch on top of LXD. This moves a lot of code around to make it more testable and easier to plug in a new database implementation in preparation for some clustering features. We’ve done a few minor improvements like adding a new “lxc operation” command, letting users peak into what LXD is currently doing in the background.
LXD Weekly Status #22
Another pretty quiet week for LXD as we keep working on a number of larger features that aren’t ready to land yet. Now that the Ubuntu 18.04 development release is open for contributions, we’re pushing LXD 2.19, LXC 2.1.1 and LXCFS 2.0.8 there which will then trickle down to our various PPAs, stable Ubuntu releases and backports.
LXD Weekly Status #21: Console Attach, Distribution Work, & More
Last week @brauner and @stgraber were traveling to Prague for the Open Source Summit Europe. We got the opportunity to talk about LXD, system containers and various bits of ongoing kernel work as well as meet with a number of our users and contributors! All this travel and conference time reduced our ability to do feature work this week, so we’ve mostly been reviewing contributions and pushing a number of bugfixes with things going back to normal this week.
LXD Weekly Status #20: Authentication, Conferences & More
This week was busy with stable releases. All in all, we released: We’ve also merged support for external authentication in LXD, through support of macaroon authentication tokens. This will make it possible to integrate LXD with enterprise SSO solutions. Initial support for SR-IOV devices has also been added. Right now adding support for dynamic allocation of SR-IOV network devices. We will soon follow that with infiniband support too.
LXD Weekly Status #19
This past week, part of the team was back in New York for more planning meetings, getting the details of the next 6 months, including LXC, LXD and LXCFS 3.0 fleshed out. The rest of the team made good progress on some smaller feature work, started working on console attach for LXD, looked into SR-IOV passthrough of network cards and infiniband devices and fixed a good chunk of bugs in LXD and LXC.
LXD Weekly Status #17
Weekly status for the week of the 25th of September to the 1st of October 2017. This past week the entire LXD team was working together in New York city. We used this opportunity to talk about our next round of LTS releases, LXC 3.0, LXD 3.0 and LXCFS 3.0, all to be released early next year. What kind of breaking changes we may want to do at that time and how we expect support to work for them.
LXD Weekly Status #16
Weekly status for the week of the 18th to the 24th of September 2017. The main highlight of this week was the release of LXD 2.18. We’ve otherwise been busy tracking down and fixing a number of issues, extended the user-agent string that LXD uses when talking to our image server and been working on a number of fixes for LXC 2.1. We’re also making good progress on the stable release branches and hope to get to tag a number of stable bugfix releases next week.
LXD: Weekly Status #15
This week has been pretty quiet as far as upstream changes since half the team was attending the Open Source Summity, the Linux Plumbers Conference and the Linux Security Summit in Los Angeles, California. We got to talk with other container runtime maintainers, kernel developers and users, having a lot of very productive discussions that should lead to a number of exciting features going forward.
LXD: Weekly status #14
The highlight for this week is the release of LXC 2.1 which is the result of a year and a half of development making up 1528 commits by 96 contributors! We’ve also been working on LXD performance testing with lxd-benchmark getting expanded to record more data points and log in a format that we can generate statistics from. This is now running daily on our Jenkins.
LXC 2.1 has been released
The LXC team is proud to announce the release of LXC 2.1. This release contains a lot of new features introduced since the release of LXC 2.0. Note that this isn’t a LTS release and we’ll therefore only be supporting LXC 2.1 for a year. Production environments that require longer term support should remain on LXC 2.0 which is supported until June 2021.
LXD Weekly Status #13: Snap data migration, Open Source Summit & more
Weekly status for the week of the 28th to the 3rd of September 2017. The main focus for this past week has been the preparation for LXC 2.1. We’ve now issued a call for testing and expect it to release tomorrow (Tuesday). On the LXD side of things, we’ve been working through bug reports quite a bit, did some internal refactoring and been slowly working our way through our stable branch backlog.
LXD Weekly Status 12
This article originally appeared at the Linux Containers forum This week saw the release of LXD 2.17 and it’s now quickly rolling out to our users. We’re still very busy with preparation work for LXC 2.1 with a tentative release date of Monday next week. A lot of work has gone into our snap package, including Open vSwitch support, a number of new configuration options and debug options.
LXD 2.17 has been released
Stéphane Graber is the technical lead for LXD at Canonical Ltd. He is the upstream project leader of LXC and LXD and is deeply involved in the container world. Stéphane has been involved with Ubuntu for years and currently sits on the Ubuntu Technical Board and Ubuntu Developer Membership board. He is a member of the Ubuntu Release team as well as an Ubuntu Archive administrator and Ubuntu Stable Release team member.
LXD: Weekly status #11
This week has been pretty busy, with the most time consuming work being: 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.
LXD: Weekly Status #10
Christian Brauner (@brauner) and Stéphane Graber (@stgraber) were attending Debconf17 in Montreal. We had the opportunity to catch up with colleagues, friends and users. Stéphane gave a talk about LXD and system containers on Debian, a recording is available: Senthil Kumaran S of Linaro was also presenting LXC on Debian: As we still have a number of slots available for the containers micro-conference at Linux Plumbers 2017, we’ve decided to extend the CFP. All current proposals have been approved.
Custom user mappings in LXD containers
As you may know, LXD uses unprivileged containers by default. The difference between an unprivileged container and a privileged one is whether the root user in the container is the “real” root user (uid 0 at the kernel level). The way unprivileged containers are created is by taking a set of normal UIDs and GIDs from the host, usually at least 65536 of each (to be POSIX compliant) and mapping those into the container.
Custom user mappings in LXD containers
As you may know, LXD uses unprivileged containers by default. The difference between an unprivileged container and a privileged one is whether the root user in the container is the “real” root user (uid 0 at the kernel level). The way unprivileged containers are created is by taking a set of normal UIDs and GIDs from the host, usually at least 65536 of each (to be POSIX compliant) and mapping those into the container.
The LXD 2.0: Blog post series [0/12]
As we are getting closer and closer to tagging the final releases of LXC, LXD and LXCFS 2.0, I figured it would be a good idea to talk a bit about everything that went into LXD since we first started that project a year and a half ago. This is going to be a blog post series similar to what I’ve done for LXC 1.0 a couple years back. The topics that will be covered are: I’m hoping to post a couple of those every week for the coming month and a half leading to the Ubuntu 16.04 release.
USB hotplug with LXD containers
It can be pretty useful to pass USB devices to a container. Be that some measurement equipment in a lab or maybe more commonly, an Android phone or some IoT device that you need to interact with. Similar to what I wrote recently about GPUs, LXD supports passing USB devices into containers. Again, similarly to the GPU case, what’s actually passed into the container is a Unix character device, in this case, a /dev/bus/usb/ device node.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Stéphane
Contact Stéphane, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack