An error is reported when docker deletes an image. After docker images, the output is as follows:
REPOSITORY TAG IMAGE ID CREATED SIZE
nvidia/cuda 9.0-base 74f5aea45cf6 6 weeks ago 134MB
paddlepaddle/paddle 1.1.0-gpu-cuda8.0-cudnn7 b3cd25f64a2a 8 weeks ago 2.76GB
hub.baidubce.com/paddlepaddle/paddle 1.1.0-gpu-cuda8.0-cudnn7 b3cd25f64a2a 8 weeks ago 2.76GB
paddlepaddle/paddle 1.1.0-gpu-cuda9.0-cudnn7 0df4fe3ecea3 8 weeks ago 2.89GB
hub.baidubce.com/paddlepaddle/paddle 1.1.0-gpu-cuda9.0-cudnn7 0df4fe3ecea3
The first image directly docker RMI 74f5aea45cf6 will be deleted successfully. However, the latter two images appear in pairs. The direct docker RMI deletion fails. The error message is as follows:
Error response from daemon:
conflict: unable to delete b3cd25f64a2a (must be forced) - image
is referenced in multiple repositories
Solution:
First, specify the name instead of the image ID when docker RMI, and then execute docker RMI – f image IDJ:
docker rmi paddlepaddle/paddle:1.1.0-gpu-cuda8.0-cudnn7
docker rmi -f b3cd25f64a2a
Read More:
- Docker delete error response from daemon: Conflict: unable to delete xxxxx solution
- Error response from daemon: Conflict: unable to delete 8598c91556dc (must be forced)
- docker Error response from daemon: Bad response from Docker engine
- docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled
- [Sovled] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
- When docker creates a container command: Error response from daemon: No command specified
- docker: Error response from daemon: driver failed programming external connectivity on endpoint
- docker: Error response from daemon: driver failed programming external connectivity on endpoint lamp
- The docker runtime container reported an error: error response from daemon: OCI runtime create failed
- Docker creation container cannot find network card: error response from daemon: network XXXX not found
- How to Fix ERROR: Couldn’t connect to Docker daemon at http+docker://localhost – is it running?
- Docker was unable to connect to the docker daemons
- Error response from daemon for private harbor login
- Error response from daemon: failed to parse mydockerfile-centos: ENV must have two arguments
- Docker compose reports an error and multiple containers conflict
- Error response from daemon: OCI runtime create failed: container_linux.go:380
- Error response from daemon: Get https://20.0.0.100/v2/: dial tcp 20.0.0.100:443: connect: connection
- This error may also indicate that the docker daemon is not running.
- Docke Run: response from daemon: OCI runtime create failed: container with id exists:XXX:unknown
- About WLW (Windows Live Writer): “unable to connect to your log service: invalid server response” solution