Writing to say that I’m affected by this bug as well. Docker is unable to start any containers as a result. To me, I think this is grounds to raise the severity of this bug to at least `serious`.
Version 2.1.4~ds2-7 of containerd was installed for me yesterday. # grep containerd /var/log/dpkg.log* /var/log/dpkg.log:2026-03-21 18:07:03 upgrade containerd:amd64 1.7.24~ds1-10 2.1.4~ds2-7 /var/log/dpkg.log:2026-03-21 18:07:03 status half-configured containerd:amd64 1.7.24~ds1-10 /var/log/dpkg.log:2026-03-21 18:07:03 status unpacked containerd:amd64 1.7.24~ds1-10 /var/log/dpkg.log:2026-03-21 18:07:03 status half-installed containerd:amd64 1.7.24~ds1-10 /var/log/dpkg.log:2026-03-21 18:07:03 status unpacked containerd:amd64 2.1.4~ds2-7 /var/log/dpkg.log:2026-03-21 18:07:22 configure containerd:amd64 2.1.4~ds2-7 <none> /var/log/dpkg.log:2026-03-21 18:07:22 status unpacked containerd:amd64 2.1.4~ds2-7 /var/log/dpkg.log:2026-03-21 18:07:22 status half-configured containerd:amd64 2.1.4~ds2-7 /var/log/dpkg.log:2026-03-21 18:07:22 status installed containerd:amd64 2.1.4~ds2-7 The error is reproducible for me by simply attempting to run the `hello-world` container. $ docker run hello-world docker: Error response from daemon: failed to create task for container: failed to start shim: failed to resolve runtime path: runtime "io.containerd.runc.v2" binary not installed "containerd-shim-runc-v2": file does not exist: unknown. Which is strange because the binary IS installed by containerd: # dpkg -S containerd-shim-runc-v2 containerd: /usr/lib/containerd/containerd-shim-runc-v2 Is there a symlink missing from one of the `bin`s in PATH? Please advise. Thank you!
