Arch Linux

Deau

Member

Registered: 2010-06-10

Posts: 7

[SOLVED] Possible docker dependency mismatch with containerd

Recently my docker service started failing with the following journal entry:

level=fatal msg="bad listen address format /var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address"

This appears to have been caused by a recent upgrade to containerd-0.2.3-1-x86_64. Fortunately I had the previous version available at /var/cache/pacman/pkg/containerd-0.2.2-1-x86_64.pkg.tar.xz.

Downgrading the containerd package solved the problem for me:

pacman -U /var/cache/pacman/pkg/containerd-0.2.2-1-x86_64.pkg.tar.xz

Posting here incase anyone else is seeing the same issue.

Last edited by Deau (2016-08-19 11:11:50)

marmotz

Member

Registered: 2016-08-18

Posts: 2

Re: [SOLVED] Possible docker dependency mismatch with containerd

Same issue here.
Your solution work for me, thank you

MaikuMori

Member

From: Latvia

Registered: 2013-05-29

Posts: 14

Website

Re: [SOLVED] Possible docker dependency mismatch with containerd

Same issue, the "fix" worked for me.

ovear

Member

Registered: 2016-08-18

Posts: 6

Re: [SOLVED] Possible docker dependency mismatch with containerd

The same problem, works fine.
This version can be found at https://archive.archlinux.org/packages/ … pkg.tar.xz

elelay

Member

Registered: 2016-08-18

Posts: 1

Re: [SOLVED] Possible docker dependency mismatch with containerd

Same problem, same solution

z3ntu

Member

Registered: 2016-01-02

Posts: 14

Re: [SOLVED] Possible docker dependency mismatch with containerd

As elelay said so nicely:
Same problem, same solution.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,303

Re: [SOLVED] Possible docker dependency mismatch with containerd

I did not see any talk of generating a bug report.   A cursory look at https://bugs.archlinux.org/ indicates that has not happened as yet.
Might I suggest that one of you generate a report?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,279

Re: [SOLVED] Possible docker dependency mismatch with containerd

It actually has https://bugs.archlinux.org/task/50430

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,303

Re: [SOLVED] Possible docker dependency mismatch with containerd

I did say cursory    But my search term docker did come up empty.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,279

Re: [SOLVED] Possible docker dependency mismatch with containerd

You were likely in the "Arch Linux" project in the upper left. Common issue, docker/containerd are in Community, so it's filed in the "Community packages" project.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,303

Re: [SOLVED] Possible docker dependency mismatch with containerd

Yep.  That is what I did.
Thanks.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

woainba15

Member

Registered: 2008-10-05

Posts: 2

Re: [SOLVED] Possible docker dependency mismatch with containerd

Works for me. thanks

marmotz

Member

Registered: 2016-08-18

Posts: 2

Re: [SOLVED] Possible docker dependency mismatch with containerd

docker was updated and now all is working for me with containerd 0.2.3-1 and docker 1:1.12.1-1

Deau

Member

Registered: 2010-06-10

Posts: 7

Re: [SOLVED] Possible docker dependency mismatch with containerd

Likewise, this issue is solved for me now. As the containerd and runc packages aren't used by the new docker package I took the following steps to keep things clean:

pacman -Rs docker    # remove docker and unused dependencies
pacman -S docker