Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [Solved] Docker service not starting after containerd update (Read 1873 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[Solved] Docker service not starting after containerd update

Containers stopped run after update.
Code: [Select]
Error response from daemon: start failed fork/exec /usr/bin/containerd-shim-runc-v2: no such file or directory: unknown
After the reboot, the docker service also stopped starting.
I have Artix runit.
Rolled back to 1.5.9-2 - everything became normal.
Any ideas how to upgrade and make it work?
Sory for bad english.

Re: Docker service not starting after containerd update from 1.5.9-2 to 1.6.0-1

Reply #1 –
https://github.com/archlinux/svntogit-community/commit/9fd350a8e67a7d0016ad450a6713c2078fd8f1d9#comments

1.6.0-1 has an error in packaging, wait for 1.6.0-2 to reach the mirrors. If you can't wait, install containerd from [community]:
Code: [Select]
# pacman -Sy community/containerd

Re: Docker service not starting after containerd update from 1.5.9-2 to 1.6.0-1

Reply #2 –
Currently I am fixing this and will be fixed soon, and once mirrors sync

Re: Docker service not starting after containerd update from 1.5.9-2 to 1.6.0-1

Reply #3 –
Thank you all very much.