Problem Description:
after the docker is closed abnormally, the following error is reported when starting the container:
linux> Error response from daemon: mkdir /run/containerd/io.containerd.runtime.v1.linux/moby/189aafa489967asdf23664d32f9e33e121a7b3b6e789d8642345678dfg6ebe13cb: file exists: unknown
linux> Error: failed to start containers: asdf
Solution:
# excute
linux> ps aux | grep 189aafa489967asdf23664d32f9e33e121a7b3b6e789d8642345678dfg6ebe13cb
# output
linux> root 6358 0.0 0.0 108748 4136 ? Sl Oct27 1:50 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/189aafa489967asdf23664d32f9e33e121a7b3b6e789d8642345678dfg6ebe13cb -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-nvidia
# Kill off and restart the container
kill 6358
Read More:
- [Solved] Docker Install Error: [Errno 14] curl#60 – Peer‘s Certificate issuer is not recognized
- Linux Install Docker Error: Failed to restart docker.service: Unit docker.service not found.
- How to Solve Docker delete container image error: Error response from daemon: conflict: unable to delete 7cc1942f1ed5 (must be forced)
- [Solved] Win 10 VS Code Connect to the container of the server error: Cannot connect to the Docker daemon at … Is the docker daemon running
- Docker Error: error invoking remote method ‘docker-start-container‘: error: (http code 500) server error –
- Docker Run ‘echo core ＞ /proc/sys/kernel/core_pattern‘ Error
- Docker Startup Error: standard_init_linux.go:211: exec user process caused “no such file or directory”
- The docker export container cannot be run after being imported: error response from daemon: no command specified
- [Solved] CUDA driver version is insufficient for CUDA runtime version
- [Solved] error:getaddrinfo ENOTFOUND xxx.xxxx.com xxx.xxxx.com:443
- docker-compose -version Run Error [How to Fix]
- Docker pull Command Error response from daemon: Head https://registry-1.docker.io/v2/library/
- Aliyunshield occupies port 80 error: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
- How to Solve NPM Error: listen EADDRINUSE 127.0.0.1:8080
- [Solved] Web server failed to start. Port 8080 was already in use.
- Vector series in actual C + +_ To_ fit()
- The solution of insufficient disk space of docker in Ubuntu
- [Solved] Linux Mongodb Error: # Error: coul-bash: connecting: command not found
- See system logs and ‘systemctl status docker.service‘ for details
- PM2 user defined Log, PID and other Log File Locations