删除none的镜像，要先删除镜像中的容器。要删除镜像中的容器，必须先停止容器。

1
2
3
4
5
6
7
8
9
10
11
12
13
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
<none> <none> 168b258ceea3 34 seconds ago 460.6 MB
<none> <none> b2c5d34941c6 23 minutes ago 588.7 MB
tankzhang /es v1 85fc66558c37 13 days ago 352.1 MB
elasticsearch latest d781cd4e3228 3 weeks ago 352.1 MB
centos latest 8140d0c64310 3 weeks ago 192.6 MB
hello-world latest 48b5124b2768 4 months ago 1.84 kB
tankzhang /es v2 48b5124b2768 4 months ago 1.84 kB
  
$ docker rmi $(docker images | grep "none" | awk '{print $3}' )
Error response from daemon: conflict: unable to delete b2c5d34941c6 (must be forced) - image is being used by stopped container ad0032609294
Error response from daemon: conflict: unable to delete 168b258ceea3 (must be forced) - image is being used by stopped container 1b7067e19d6f

直接删除带none的镜像，直接报错了。提示先停止容器。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
$ docker stop $(docker ps -a | grep "Exited" | awk '{print $1 }' )  // 停止容器
1b7067e19d6f
a840f345c423
9d74eff1c4e4
17d361107a21
dd51ead96da7
ad0032609294
95e713ab1bdf
  
$ docker rm $(docker ps -a | grep "Exited" | awk '{print $1 }' )  // 删除容器
1b7067e19d6f
a840f345c423
9d74eff1c4e4
17d361107a21
dd51ead96da7
ad0032609294
95e713ab1bdf
  
$ docker rmi $(docker images | grep "none" | awk '{print $3}' )  // 删除镜像
Deleted: sha256:168b258ceea3f5ee9d7f066e04c89c4858f0e337687f18b5939a78aea13ea6c8
Deleted: sha256:d3984014bcbe856f569dcade31ce70aae8cc5ead3806e47ae08229467c9ed3ca
Deleted: sha256:b2c5d34941c646a1962d2acd9ff968708495a82916c33797f5fb3d94de403c6d
Deleted: sha256:5a23f5ad9107bb1111f32d490982e2146cf0811c8b75c7a6cd67ca45fc2f50dd
Deleted: sha256:392d616344b17b0bb7b8ad46cc9a8c6f5ab4be8bd59c3d5973016e8759a1668c
Deleted: sha256:33fbf9c999e8beac51b184a0f2baeaf1a2b99b10c4cc1f654075af42779fb62e
Deleted: sha256:b3535d64be668cd7e3389c4da224ae6e3aaedadff05ed24f428fc83e96c65a03
Deleted: sha256:da47261567b38193ba4894e7c832d9eba78d9cc3a501101ebf5fd7304efef5b9
Deleted: sha256:b81b2578fd4e803fac0bd416e606362ed14432370088eba8bf5c43a4fca8f7ed
Deleted: sha256:6f4b2f9fd5be471ac80c599c9616feaaf3952ce8a68d5d8c26645bfaff7aae4a
Deleted: sha256:480e2b77d27aea6e128db8d3c400f37b74da1b365b0eb663022d7208a9694209

原文：http://www.jb51.net/article/116096.htm


Logo
向您推荐>>Eolink开发者社区

权威｜前沿｜技术｜干货｜国内首个API全生命周期开发者社区

更多推荐

ELK实现containerd的容器日志采集展示【基于logging的全栈监测】

企业级ELK Stack构建介绍

avatar 云原生

深入理解 Mocha 测试框架：从零实现一个 Mocha

前言什么是自动化测试自动化测试在很多团队中都是Devops环节中很难执行起来的一个环节，主要原因在于测试代码的编写工作很难抽象，99%的场景都需要和业务强绑定，而且写测试代码的编写工作量往往比编写实际业务代码的工作量更多。在一些很多业务场景中投入产出比很低，适合写自动化测试的应该是那些中长期业务以及一些诸如组件一样的基础库。自动化测试是个比较大的概念，其中分类也比较多，比如单元测试，端对端测试，集

avatar 云原生

(20200916 Solved)docker-compose up创建容器自动退出

问题描述如题，创建容器后自动退出了。并且docker start container无效解决方案原因是缺失了控制终端的配置，需要在docker-compose.yml中增加tty:true ，有时候这样也不行，需要再增加一个command:/bin/bash，命令不一定是这个，需要是一个不会退出的命令，然后用-d后台启动容器。Referencesdocker-compose启动容器后自动退出...

avatar 云原生