I had remove all images and remove container but still have one cannot removed,the error message is :
Error response from daemon: container ac19d83b3b596bf8a995ce99500b12a0881ae4e1af067aaa2063dfcceb5a4314:
driver "overlay2" failed to remove root filesystem:
remove/var/lib/docker/overlay2/a64ec712b637a9c245a4213e3b97aaeacd3c04d7218b4b7902ec3a5e75bb33fb/diff/home/wwwroot/default/.user.ini: operation not permitted
my docker info :
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 0
Server Version: 18.06.0-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d64c661f1d51c48782c9cec8fda7604785f93587
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-30-generic
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.689GiB
Name: Blank
ID: CG5D:XHVM:6QCM:ENF5:GDJ5:GHSD:6VU4:UOPM:2RCC:QMH5:WKNM:IZTZ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
How can I fix
Even trying to remove it with the -f option isn't working for you?
This should remove all containers:
docker rm -f $(docker ps -a -q)
Related
I’m trying to use the command:
RUN apt-get update
inside a dockerfile, but this command just hangs forever and there is no response after it.
Also, if I try to exit from the build, the whole computer is stuck and can’t be rebooted (the dockerd process becomes zombie which apparently affects the whole system).
I thought it could be related to network issues because it start happening after my system (Ubuntu 16.04) couldn’t connect to the wifi for some time.
Also, I changed the default data-root folder used to store images and containers, and when I'm trying to restore this option to the original one (store the images and containers in /var/lib/docker), it is working again (the command doesn't hang).
Here are my docker details:
Client:
Debug Mode: false
Server:
Containers: 10
Running: 2
Paused: 0
Stopped: 8
Images: 4
Server Version: 19.03.9
Storage Driver: aufs
Root Dir: /media/DATA/Docker-Root/aufs
Backing Filesystem: <unknown>
Dirs: 42
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-50-generic
Operating System: Ubuntu 16.04.6 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.34GiB
Name: demo2
ID: GQ56:YN4L:DIIG:WRV4:MKI4:YM35:JUJP:3KKA:K3QO:374J:IHFS:6UCZ
Docker Root Dir: /media/DATA/Docker-Root
Debug Mode: false
Username: rang
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
WARNING: the aufs storage-driver is deprecated, and will be removed in a future release.
I had an issue with docker running on a raspberry pi 4 and I purged all of it apart from the folder with the containers/images.
Reinstalled docker, run helloworld, runs ok. Installed portainer to manage the containers, several of them start but a particular one, homeassistant, doesn't
It reports
pi#raspberrypi:~ $ docker start homeassistant
Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/7c4732337e167e0f8178b8667bddc0393c2c1e4f7ffba5d68fe57379cc1de7c0/merged: no such file or directory
Error: failed to start containers: homeassistant
Here's the result of docker info
pi#raspberrypi:~ $ docker info
Client:
Debug Mode: false
Server:
Containers: 7
Running: 4
Paused: 0
Stopped: 3
Images: 32
Server Version: 19.03.8
Storage Driver: overlay2
Backing Filesystem: <unknown>
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.19.97-v7l+
Operating System: Raspbian GNU/Linux 10 (buster)
OSType: linux
Architecture: armv7l
CPUs: 4
Total Memory: 3.814GiB
Name: raspberrypi
ID: CS34:4SMJ:FTCR:T3O3:JVWH:LNEC:RWIE:2D7X:435Z:4WHM:UZZZ:CMS3
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Here are the contents of the overlay folder
pi#raspberrypi:~ $ sudo ls /var/lib/docker/overlay2/7c4732337e167e0f8178b8667bddc0393c2c1e4f7ffba5d68fe57379cc1de7c0/
diff link lower work
I've checked the overlay2 folder and indeed there's no merged folder. I've tried creating an empty one, but it gets deleted as soon as I attempt starting the container. What does this folder indicate when it comes to the container and how do I work around it? Ideally I would like to keep the container as otherwise I would have to set up the whole thing again.
I'm trying to pull an image from Docker Hub (this one: https://hub.docker.com/r/openmicroscopy/omero-server/). When I run docker pull openmicroscopy/omero-server I get the following output:
Using default tag: latest
latest: Pulling from openmicroscopy/omero-server
5e35d10a3eba: Already exists
4c7f892860a0: Pull complete
8eef538af010: Pull complete
7ce54f93fa6f: Pull complete
67e4ee84001a: Extracting 581MB/581MB
873bd90af4ef: Download complete
2c29661b3a9e: Download complete
eb230c33fb76: Download complete
failed to register layer: Error processing tar file(exit status 1): write /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/lib/rt.jar: no space left on device
I have enough space left. However, when I watch df -i I do see that my /var inode usage briefly goes to 100%, after which the process ends with the error message shown above.
Docker info:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 2
Server Version: 18.03.1-ce
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Native Overlay Diff: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: nvidia runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-514.26.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 62.71GiB
Name: cn1147.irc.ugent.be
ID: F52F:JVNR:XL6V:7UED:AGIS:H3VW:GN54:YBYR:SY3Q:QGPK:K45X:NVYU
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Docker version: Docker version 18.03.1-ce, build 9ee9f40
As you can see in the info output I'm using overlay2, which should not suffer from any inode issues. Any ideas?
Thanks!
Not able to use docker run in Amazon Linux AMI
docker run hello-world
docker:
Error response from daemon: unable to find "pids" in controller set:
unknown. ERRO[0000] error waiting for container: context canceled
docker info
{ # docker info
Containers: 6
Running: 0
Paused: 0
Stopped: 6
Images: 2
Server Version: 18.06.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:
runc version:
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.14.72-68.55.amzn1.x86_64
Operating System: Amazon Linux AMI 2018.03
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.79GiB
Name: ip-172-31-0-234
ID: AGTD:BUGU:RDRN:CSHC:INSH:HCMG:QFYT:OUNC:NCVZ:UDAM:PJYS:3ZQM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: magsgfin
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
}
Currently, Amazon Linux is not supported distribution. There are't any official packages for that distro moreover, docker it is not tested on it.
It seems this error is raised by cgroups package
You can try to run this script to check if anything is missing or misconfigured.
I meet the problem when running the deploy sh of Shipyard. The error is
docker: Error response from daemon: driver failed programming external connectivity on endpoint shipyard-proxy (): Bind for 0.0.0.0:2375 failed: port is already allocated.
Then I use netstat -ntple command to find out who is listening port 2375.
The result is dockerd itself.
So I wonder how to overcome this problem in order to finish the installation of Shipyard.
And here is the docker ps
My docker info result is showed below
Containers: 8
Running: 4
Paused: 0
Stopped: 4
Images: 21
Server Version: 17.12.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9b55aab90508bd389d7654c4baf173a981477d55
runc version: 9f9c96235cc97674e935002fc3d78361b696a69e
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.13.0-37-generic
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 962.8MiB
Name: flora-virtual-machine
ID: J765:X2HP:UL4S:2SCV:7CZK:LG63:4H5V:QFDF:RUM5:2F2Y:XC6I:Y3AE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Registry Mirrors:
http://4d7846d0.m.daocloud.io/
Live Restore Enabled: false