Docker删除容器错误

时间:2016-12-23 15:17:58

标签: docker

当我想用其他卷重新运行容器或更新映像时。 我停下来尝试删除容器,但通常是rm命令

上的geterror
# docker rm containername

Error response from daemon: Driver devicemapper failed to remove root filesystem dbe6....f91f: Device is Busy

我需要重启docker守护进程才能删除容器。

~ # docker version                                                                                                           root@CentOS-72-64-minimal
    Client:
     Version:      1.12.5
     API version:  1.24
     Go version:   go1.6.4
     Git commit:   7392c3b
     Built:        Fri Dec 16 02:23:59 2016
     OS/Arch:      linux/amd64

    Server:
     Version:      1.12.5
     API version:  1.24
     Go version:   go1.6.4
     Git commit:   7392c3b
     Built:        Fri Dec 16 02:23:59 2016
     OS/Arch:      linux/amd64
    ------------------------------------------------------------
~ # docker info                                                                                                              root@CentOS-72-64-minimal
    Containers: 40
     Running: 11
     Paused: 0
     Stopped: 29
    Images: 32
    Server Version: 1.12.5
    Storage Driver: devicemapper
     Pool Name: docker-8:3-28705145-pool
     Pool Blocksize: 65.54 kB
     Base Device Size: 10.74 GB
     Backing Filesystem: xfs
     Data file: /dev/loop0
     Metadata file: /dev/loop1
     Data Space Used: 14.83 GB
     Data Space Total: 107.4 GB
     Data Space Available: 92.54 GB
     Metadata Space Used: 21.15 MB
     Metadata Space Total: 2.147 GB
     Metadata Space Available: 2.126 GB
     Thin Pool Minimum Free Space: 10.74 GB
     Udev Sync Supported: true
     Deferred Removal Enabled: false
     Deferred Deletion Enabled: false
     Deferred Deleted Device Count: 0
     Data loop file: /var/lib/docker/devicemapper/devicemapper/data
     WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
     Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
     Library Version: 1.02.135-RHEL7 (2016-09-28)
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Plugins:
     Volume: local
     Network: bridge overlay host null
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Security Options: seccomp
    Kernel Version: 3.10.0-514.2.2.el7.x86_64
    Operating System: CentOS Linux 7 (Core)
    OSType: linux
    Architecture: x86_64
    CPUs: 8
    Total Memory: 30.96 GiB
    Name: CentOS-72-64-minimal
    ID: SMTY:72HJ:5QIS:AT63:6GPI:U2UQ:KUYY:C7M6:UIOY:37AR:JS53:JAGA
    Docker Root Dir: /var/lib/docker
    Debug Mode (client): false
    Debug Mode (server): false
    Registry: https://index.docker.io/v1/
    WARNING: bridge-nf-call-iptables is disabled
    WARNING: bridge-nf-call-ip6tables is disabled
    Insecure Registries:
     127.0.0.0/8                           

2 个答案:

答案 0 :(得分:1)

我在Red Hat主机上遇到过这个问题。根据报告的问题修复此问题是升级到更新的内核。作为一个不可选择的地方的解决方法,我一直在使用docker rm -f ...,它仍然会抛出错误,但容器会被清理干净。比重启守护进程更快,更少侵入。

答案 1 :(得分:0)

我遇到了同样的问题,import csv a={'1':{'0.9'}, '2':{'0.6'},'3':{'0.5'}} b = dict(zip(a.keys(), map(lambda x: next(iter(x)), a.values()))) with open('new_file','w') as f: writer = csv.writer(f) writer.writerows(b.items()) 几乎总能解决问题。(重启docker服务)

有关此问题的更多信息,请访问here