Why I can't rm docker image?

So my question is,I run container B from image B but why docker say the container B is using image A when I want rmi image A.

My docker version:

Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64

  • Logstash syslog input from docker container
  • Does it make sense to install the runtime on docker?
  • Can I use Docker for production deployment of a Rails application?
  • Docker's containers communication using Consul
  • pyftpdlib Networkprotocol Error
  • How to run docker-compose in Azure Container Service and deploy to agent rather than master?
  • 2 Solutions collect form web for “Why I can't rm docker image?”

    Your image B is based on image A. It inherits all the image layers used in image A. And it adds the new image layer that you created by committing your new image B.

    So image A remains always in your image layer revision tree as a dependency when you use image B. As long as you have a running container using image B you cannot delete image A.

    This is exactly the intended behavior. You have effectively created a Layer(Image) B on top of Layer(Image) A.

    Where Layer B is the delta of the operations on Layer A. This is based on the Union File System and is described in the context of docker at: Understanding Docker

    I would say that you are now running container B, which is depending on ImageA (Providing the error). However the root issue is that Image B depends on ImageA.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.