Docker issues on 42680; rollback to 41840 [resolved]

General Discussion
1

I’m seeing docker issues again:

$sudo swupd update
Update started
Version on server (42680) is not newer than system version (42680)
Update complete - System already up-to-date at version 42680

$ uname -a
Linux books.box 6.11.6-1477.native #1 SMP Thu Oct 31 18:41:56 PDT 2024 x86_64 GNU/Linux

$ docker image ls quay.io/vektorlab/ctop
REPOSITORY               TAG       IMAGE ID       CREATED       SIZE
quay.io/vektorlab/ctop   latest    ed869812e1a4   2 years ago   13.2MB

$ cat ctop
#!/usr/bin/env bash

docker stop ctop

docker run --rm -ti \
  --name=ctop \
  --volume /var/run/docker.sock:/var/run/docker.sock:ro \
  quay.io/vektorlab/ctop:latest

$ ./ctop 
Error response from daemon: No such container: ctop
docker: Error response from daemon: failed to create task for container: failed to start shim: start failed: unsupported shim version (3): not implemented.
ERRO[0000] error waiting for container:

Using a rollback script to 41840 makes things work again:

cat rollback-docker.sh 
#!/usr/bin/env bash
# a script to rollback docker to a currently working version

VERSION=41840

sudo swupd repair --verbose --version $VERSION --bundles=containers-basic --force
sudo swupd autoupdate --disable
cat /etc/os-release
2

When you updated you appear to have only restarted the docker service and not the containerd service.
sudo systemctl restart containerd.service

3

Thanks for the suggestion. The containerd.service was disabled across 4 servers and appears to coincide with the 41840 → 42680 autoupdate.

So, a quick sudo systemctl enable containerd and sudo swupd autoupdate --enable to revert my previous adjustment and it looks like we’re back in business