Docker containers fail with "failed to create TTRPC connection: unsupported protocol:Yunix" on EndeavourOS

Hi, I’m on EndeavourOS and my Docker setup suddenly stopped being able to start any containers. My main goal is to get docker run --rm hello-world working again so I can safely back up and then migrate my containers to docker-compose.


Whenever I try to run a container, I get:

docker run --rm hello-world
docker: Error response from daemon: failed to create task for container: failed to start shim: start failed: failed to create TTRPC connection: unsupported protocol:Yunix.

The same happens when I start containers via docker compose up -d.


What I’m running**:**

  • Distro: EndeavourOS (with CachyOS repos installed), fully updated via sudo pacman -Syu

  • Docker and containerd: installed from official repos (pacman -S docker containerd)

  • containerd binaries:

    • /usr/bin/containerd

    • /usr/bin/containerd-shim-runc-v2

    • no containerd-shim or docker-containerd-shim in /usr/local/bin

  • /etc/docker/daemon.json does not exist


What I’ve already tried

  • Restarted Docker multiple times:

sudo systemctl restart docker

Service is active, but any docker run fails with the error above.

  • Fully updated and reinstalled docker + containerd:
sudo pacman -Syu docker containerd
sudo pacman -Rns docker containerd
sudo pacman -S docker containerd

Then:

sudo systemctl enable --now docker

Still get the same TTRPC / shim error.

  • Confirmed there is no custom daemon config:
cat /etc/docker/daemon.json
# -> No such file or directory
  • Checked for stray shims in /usr/local/bin and found none.

What I need help with:

  • How to properly debug and fix this failed to create TTRPC connection: unsupported protocol:Yunix error on EndeavourOS.
  • What logs or configuration files I should share (e.g., full journalctl -xeu docker.service) to pinpoint whether this is a containerd/runc mismatch, cgroups issue, or a known Arch/EndeavourOS bug.

I haven’t backed up most of the things in Docker and I’m relatively new to this. It was my fault just coming in blind installling docker containers without learning about them first.

I deeply appreciate any guidance. Thank you!

I had the same issue after I did a system upgrade. A reboot solved it for me.

I facepalmed and can’t believe it’s that simple. Thank you @kviktor! Docker now works again.