compose: docker-compose up: ERROR: Cannot start container: failed to update store for object type *libnetwork.endpointCnt

Mac OS X 10.10.5

$ docker-compose up
Pulling redis (redis:2.8)...
2.8: Pulling from library/redis

1d53ee5b1800: Pull complete
74872ba2a3b0: Pull complete
b73eb536e646: Pull complete
733ba5d512e3: Pull complete
00b5a1f6aeae: Pull complete
65b0d3a3cd30: Pull complete
a46a54050037: Pull complete
344888176fa7: Pull complete
2380915c0807: Pull complete
f454f845714a: Pull complete
b04e3558e7f0: Pull complete
e25f48bc0233: Pull complete
acaeeb5be8f7: Pull complete
bdccb64d4c06: Pull complete
96288bc75a66: Pull complete
47130e6037f2: Pull complete
ca6553f7ffad: Pull complete
Digest: sha256:2e89addcd3b13e473e4302c202c0171f8e83f4d31af3bbcd8d6c3f68a31fde7c
Status: Downloaded newer image for redis:2.8
Creating rejum_redis_1
ERROR: Cannot start container 6f546315c9ad94337c201b95b22668549d27423b850c366a30de66c46a9c7372: 
failed to update store for object type *libnetwork.endpointCnt: Key not found in store

Didn’t find any info about this error, can you explain what this means and what to do?

Do I need to show my docker-compose file?

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 15 (1 by maintainers)

Most upvoted comments

I moved my docker images folder when I faced this problem. If you use Ubuntu, just run sudo apt install --reinstall docker to fix this problem.

Svtter on Sep 15, 2018

For those suffering this issue, I reset my docker twice and it started working.

Your mileage may vary. For this and other reasons, I’m wondering if my SSD is shot although I’m not getting any errors when scanning it. 🤷🏻‍♂️

Gisleburt on May 21, 2019

Actually, I tried to re-create docker VM, and suddenly it helped. Now everything just works, without any additional actions. So, probably, this issue is deprecated and can be closed.

But would be good to know at least what this error means and why it can appear.

I am facing the same error in Linux/Ubuntu. I tried install --reinstall docker and virtualbox also but the error is still coming. Can you suggest me how to solve this??

vivekruhela on Oct 15, 2018

More than one year later and I fixed this issue restarting the docker service as @Gisleburt commented.

Its worth mention that I am using the docker service in one partition and pointing the images to another one, here is my daemon.json:

{
    "storage-driver": "overlay",
    "graph": "/mnt/aabfaa12-123s-48ab-a25d-asdas121/docker",
    "cgroup-parent": "/docker_limit.slice"
}

Then I executed: systemctl restart docker and it worked again.

marabesi on Aug 31, 2020