FS#54888 - [docker] docker: Error response from daemon: shim error: json: cannot unmarshal array into Go str...

Attached to Project: Community Packages
Opened by Carsten Pohl (archlinuxuser7719) - Thursday, 20 July 2017, 12:55 GMT
Last edited by Sébastien Luttringer (seblu) - Sunday, 23 July 2017, 23:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Can't run docker images/containers anymore.

Additional info:
* package version(s)
docker 1:17.06.0-1

* config and/or log files etc.
github docker issue:
https://github.com/moby/moby/issues/34200

Steps to reproduce:
docker run --rm -it myimage:latest

According to the docker github page,
"The problem here is that the Arch package ships the wrong version of RunC, which is incompatible with Docker 17.06;..."
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Sunday, 23 July 2017, 23:44 GMT
Reason for closing:  Not a bug
Additional comments about closing:  PEBCAK
Comment by Morten Linderud (Foxboron) - Thursday, 20 July 2017, 18:23 GMT
We are building against commit https://github.com/docker/runc/commit/2d41c047c83e09a6d61d464906feb2a2f3c52aa4 from runc, while the docker project assumes the branch `docker-master` it seems; https://github.com/docker/runc/commit/9c2d8d184e5da67c95d601382adf14862e4f2228
Comment by David Parrish (dmp1ce) - Sunday, 23 July 2017, 20:48 GMT
What is the recommended workaround for the time being?
Comment by Sébastien Luttringer (seblu) - Sunday, 23 July 2017, 21:37 GMT
I'm not affected by this. I'm building against the version defined here https://github.com/docker/docker-ce/blob/v17.06.0-ce/components/engine/hack/dockerfile/binaries-commits.
Comment by David Parrish (dmp1ce) - Sunday, 23 July 2017, 23:33 GMT
When I updated docker I did get this error but when I rebooted the issue went away. I assume if I had done a restart of docker it would have fixed it too.
Comment by Sébastien Luttringer (seblu) - Sunday, 23 July 2017, 23:44 GMT
Yes, you should have. I see the mismatch in the github bugreport.

Loading...