You are not logged in.
I updated containerd from 1.3.4-2 to 1.4.0-1, and docker (1:19.03.12-2) won't start any container anymore.
# docker run --rm -it archlinux bash
docker: Error response from daemon: ttrpc: closed: unknown.
After I downgrade containerd to 1.3.4-2, docker is working fine.
But I can't find any related bug report. Could anyone reproduce this problem?
Last edited by nyaw (2020-08-19 15:10:18)
Offline
+1
Cleared cached packages, so now looking for the way to downgrade.
Offline
We can use Arch Linux Archive.
Offline
Thanx!
Offline
Sheraff you will find containerd archive packages here: Archive Containerd
In the future if you have the same problem then go to Arch Archive Packages and navigate to your package by the name.
Offline
Ok, thanx guyz.
There's certainly an issue with a newer version of containerd.
Offline
Ran into the same issue yesterday had to revert using the archive. Deiced to check if the issue was fixed and it seems to be now.
After removing the archive I did a "pacman -Syyuu" and got "containerd 1.4.0-2" update and now all seems to be fine. Tested on two separate machines
Offline
Thanks. I updated containerd to 1.4.0-2 and solved this problem. Maybe my mirror is just out-of-sync.
Offline
I was having weird issues with a couple of containers. The Plex container wouldn't even stop properly. I was on 1.4.0-2. I downgraded to 1.3.4-2 and everything is back to normal now. Just saying, the problem might not be fixed for everyone yet.
Offline
I was having weird issues with a couple of containers. The Plex container wouldn't even stop properly. I was on 1.4.0-2. I downgraded to 1.3.4-2 and everything is back to normal now. Just saying, the problem might not be fixed for everyone yet.
Same here. On containerd-1.4.0-2 all containers that has healthchecks are reporting "unhealthy" and I can't start/stop/restart/do anything with them. Reboot solves it for some time, but after a while (maybe 2 hrs) it happens again.
Only downgrade helps. The problem is NOT solved for some users, apparently.
Offline
I just confirmed, that I see the same behaviour with the binaries from github. So this is not a problem of the Arch package.
Offline
Instead of rebooting I have been killing the left over container-shim processes.
Offline
Did anybody report the remaining issue upstream?
ArchLinux - make it simple & lightweight
Offline
i could cry i experienced exactly this problem and spent hours on this. It seems the people in there irc chat freenode #docker are currently not aware of this issue
Offline
Submitted bug report to containerd upstream.
Mods, I'd suggest breaking out this topic starting here, as it is a different issue than the OP. Thanks!
Offline