<none>: There are two types of <none> one is benign and depends on other layers when building the image. This none image is normal. One is build failure<There are various problems that cause the failure. Dockerfile file syntax error, file downloading is blocked when running, own cancellation action, etc.> This kind of none image can be cleared. After the successfully built image is pushed, you will not be able to see the benign none image after pulling.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
docker tag imageid name:tag correct solution.
In csphere, the docker management platform, you can also add tags to images online
The empty image is the "cache" during pull. Just delete it directly with docker rmi IMAGE ID.
------update-----
It turns out that this image is being used by a certain container, and the poster wants to save it. Then the steps are as follows:
docker ps -a | grep 镜像 ID# Get the ID of this image to get the correct container IDdocker commit -a 'message aaaa' CONTAINER_ID NEW_IMAGE_NAME# Save the container as a new image.docker tag IMAGEID new_repository newTAG Try this
<none>: There are two types of <none> one is benign and depends on other layers when building the image. This none image is normal.
One is build failure<There are various problems that cause the failure. Dockerfile file syntax error, file downloading is blocked when running, own cancellation action, etc.> This kind of none image can be cleared. After the successfully built image is pushed, you will not be able to see the benign none image after pulling.