Instructions on how to do dist upgrade for Debian 9 servers used by Wodby:
First, stop all Docker related services:
systemctl stop kube-apiserver
systemctl stop kube-controller
systemctl stop kube-kubelet
systemctl stop kube-proxy
systemctl stop kube-scheduler
systemctl stop dockerUpdate repositories in /etc/apt/sources.list with:
deb http://deb.debian.org/debian bullseye main
deb-src http://deb.debian.org/debian bullseye main
deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main
deb http://deb.debian.org/debian bullseye-updates main
deb-src http://deb.debian.org/debian bullseye-updates main
deb http://deb.debian.org/debian bullseye-backports main
deb-src http://deb.debian.org/debian bullseye-backports main
And the do the dist upgrade (when prompted, answer YES or select default option):
apt update
apt dist-upgrade -yUpdate iptables path in /etc/systemd/system/docker.service.d/iptables.conf
- Usually
/sbin/iptablesbecomes/usr/sbin/iptables - If you have problems, see https://wiki.debian.org/iptables
Validate dist upgrade and check the it says "Debian GNU/Linux 11 (bullseye)":
cat /etc/os-releaseDebian 11 has cgroup2 enabled that not currently supported by the docker version Wodby uses, so you should disable it:
- Edit
/etc/default/gruband addsystemd.unified_cgroup_hierarchy=0toGRUB_CMDLINE_LINUX_DEFAULT(orGRUB_CMDLINE_LINUXif it's not present) - Run
update-grub - Also check that
/lib/systemd/system/kube-kubelet.servicehas a flag--cgroups-per-qos=false
And lastly, reboot:
reboot nowAfter getting back to server with SSH:
Check that services are starting:
docker ps --format "table {{.Names}}\t{{.Status}}"On the Wodby UI check that server Status is Ok
Finally you can do cleanup:
apt --purge autoremove
apt purge `dpkg -l | grep "deb9" | awk '{print $2}'`