Docker on some occasions fails to create the network bridge at startup and thus fails to start the daemon.
dockerd: time="2020-06-04T01:45:04.544497066Z" level=error msg="c0a32b12b409421e6c629b131b5c20cfc69ead118b6a27d98610cef8d18862b8 cleanup: failed to delete container from containerd: no such container"
dockerd: time="2020-06-04T01:45:04.544547136Z" level=error msg="Handler for POST /v1.39/containers/c0a32b12b409421e6c629b131b5c20cfc69ead118b6a27d98610cef8d18862b8/start returned error:
failed to update store for object type *libnetwork.endpoint: open /var/lib/docker/network/files/local-kv.db: no such file or directory"
- Platform9 Managed Kubernetes - All Versions
This is an upstream Docker daemon issue without a proper known cause and the accepted solution in the community is the resolution mentioned below.
- Remove the Docker internal files.
sudo rm -rf /var/lib/docker
- Restart the Docker Daemon service.
sudo systemctl restart docker