kubeadm doesn't work with containerd version of apt install

Bug #1979313 reported by Fulga Fabian
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
containerd (Ubuntu)
Triaged
Low
Unassigned
Focal
Triaged
Low
Unassigned

Bug Description

Version of Ubuntu:
Description: Ubuntu 22.04 LTS
Release: 22.04

kubeadm:
  Installed: 1.24.2-00
  Candidate: 1.24.2-00

Package that has the problem:
containerd:
  Installed: 1.5.9-0ubuntu3
  Candidate: 1.5.9-0ubuntu3
  Version table:
 *** 1.5.9-0ubuntu3 500
        500 http://ro.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

Problem:
Kubeadm is not compatibile with this version of containerd that is installed by `apt install containerd`.
If I use `kubeadm init` it will create a cluster which instead of staying alive will die after a couple of minutes.
The problem is in the config file of containerd, which has the following parameter set to false: `SystemdCgroup = false`

Solution:
To solve this, the containerd config parameter SystemdCgroup needs to be set to true.
It is set to true in the containerd v1.6.2, but by default, apt installs the version v1.5.9, which worked on Ubuntu 20.04 but does not work for Ubuntu 22.04.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apt (Ubuntu):
status: New → Confirmed
Revision history for this message
trya uuum (tryauuum) wrote :

Thanks Fabian, creating a containerd config and putting `SystemdCgroup = true` there did fix it for me

By the way, how did you manage to find the cause of this issue? I want to have the same debugging skills as you do.

Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

Thanks for taking the time to report this bug and trying to make Ubuntu better.

This seems to be a real issue, in the kubernetes documentation they tell users to set this variable to true:

https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd-systemd

We are planning to update containerd to the latest upstream version which will fix this issue as you mentioned. While this does not happen here users can find a simple workaround for that.

Changed in containerd (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in apt (Ubuntu):
status: Confirmed → Invalid
Changed in containerd (Ubuntu Focal):
importance: Undecided → Low
status: New → Triaged
Changed in apt (Ubuntu Focal):
status: New → Invalid
Revision history for this message
Julian Andres Klode (juliank) wrote :

Deleted the apt task instead so comments don't go apt subscribers for all eternity.

no longer affects: apt (Ubuntu)
no longer affects: apt (Ubuntu Focal)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.