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.
** Also affects: containerd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1979313
Title:
kubeadm doesn't work with containerd version of apt install
Status in apt package in Ubuntu:
Confirmed
Status in containerd package in Ubuntu:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1979313/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
