Failed to load container mount 022183...: mount does not exist - docker

When I start docker:
service docker start
Shows this log:
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.969535655+08:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.970807372+08:00" level=info msg="Loading containers: start."
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.972484550+08:00" level=error msg="Failed to load container mount 022183ecc93800ee6af20bfa8a59ec3746568c73abbea29e3d305c46b468990c: mount does not exist"
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.972792385+08:00" level=error msg="Failed to load container mount 05073c615ef179888e689414348f026116a206987ae4e66cff04fa85435e1e70: mount does not exist"
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.973235355+08:00" level=error msg="Failed to load container mount 0857413708fdc210726d664b3c312fc65ff40448db177d9d2af545a13f91e48c: mount does not exist"
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.973572688+08:00" level=error msg="Failed to load container mount 117c3e16388063b1741fb584f10bb2f7e09508c844b661e3cb628a836094f011: mount does not exist"
Sep 15 02:05:16 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:16.973619897+08:00" level=error msg="Failed to load container 16831d8345c6ade3f96544a2bd95020841933480b4a9c96ae5d5f36a17eb310e: open /var/lib/docker/containers/16831d8345c6ade3f96544a2bd95020841933480b4a9c96ae5d5f36a17eb310e/config.v2.json: no such file or directory"
Sep 15 02:05:17 iZuf63refzweg1d9dh94t9Z dockerd[13274]: time="2019-09-15T02:05:17.167060906+08:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
docker info shows root path:
Docker Root Dir: /var/lib/docker
and container shows:
[root#iZuf63refzweg1d9dh94t9Z containers]# ls
022183ecc93800ee6af20bfa8a59ec3746568c73abbea29e3d305c46b468990c 117c3e16388063b1741fb584f10bb2f7e09508c844b661e3cb628a836094f011
05073c615ef179888e689414348f026116a206987ae4e66cff04fa85435e1e70 16831d8345c6ade3f96544a2bd95020841933480b4a9c96ae5d5f36a17eb310e
0857413708fdc210726d664b3c312fc65ff40448db177d9d2af545a13f91e48c
why the docker still do not find container?

Related

Docker image pull fails and makes docker daemon inaccessible until machine restart

I am facing a strange issue with the docker image pull command where the command fails with this error;
[desai#brilp0017 ~]$ docker image pull nginx:latest
latest: Pulling from library/nginx
d121f8d1c412: Extracting [==================================================>]
27.09MB/27.09MB
ebd81fc8c071: Download complete
655316c160af: Download complete
d15953c0e0f8: Download complete
2ee525c5c3cc: Download complete
failed to register layer: Error processing tar file(exit status 1): Error cleaning up after pivot: remove /.pivot_root534731447: device or resource busy
After this error the docker daemon is no longer accessible and all docker commands return following error;
[desai#brilp0017 ~]$ docker info
Client:
Debug Mode: false
Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
The command systemctl status docker however shows it as running;
[desai#brilp0017 ~]$ systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: active (running) since Fri 2020-09-11 14:25:53 BST; 14min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 2380 (dockerd)
Tasks: 14
Memory: 249.5M
CGroup: /system.slice/docker.service
└─2380 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
The journalctl log has the same error line as encountered in the pull command;
Sep 11 14:25:52 brilp0017 systemd[1]: Starting Docker Application Container Engine...
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.345006155+01:00" level=info msg="Starting up"
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.348597478+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.348667479+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.348733420+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.348765306+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.353865701+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.353908904+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.353944835+01:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 <nil>}] <nil>}" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.353988191+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.497701794+01:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.816295801+01:00" level=warning msg="Your kernel does not support cgroup rt period"
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.816318357+01:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Sep 11 14:25:52 brilp0017 dockerd[2380]: time="2020-09-11T14:25:52.816442165+01:00" level=info msg="Loading containers: start."
Sep 11 14:25:53 brilp0017 dockerd[2380]: time="2020-09-11T14:25:53.101411528+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Sep 11 14:25:53 brilp0017 dockerd[2380]: time="2020-09-11T14:25:53.125378601+01:00" level=info msg="Loading containers: done."
Sep 11 14:25:53 brilp0017 dockerd[2380]: time="2020-09-11T14:25:53.291896277+01:00" level=warning msg="Not using native diff for overlay2, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled" storage-driver=overlay2
Sep 11 14:25:53 brilp0017 dockerd[2380]: time="2020-09-11T14:25:53.292711063+01:00" level=info msg="Docker daemon" commit=48a66213fe graphdriver(s)=overlay2 version=19.03.12-ce
Sep 11 14:25:53 brilp0017 dockerd[2380]: time="2020-09-11T14:25:53.293190069+01:00" level=info msg="Daemon has completed initialization"
Sep 11 14:25:53 brilp0017 dockerd[2380]: time="2020-09-11T14:25:53.340381428+01:00" level=info msg="API listen on /run/docker.sock"
Sep 11 14:25:53 brilp0017 systemd[1]: Started Docker Application Container Engine.
Sep 11 14:32:38 brilp0017 dockerd[2380]: time="2020-09-11T14:32:38.011501405+01:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Sep 11 14:33:11 brilp0017 dockerd[2380]: time="2020-09-11T14:33:11.592234770+01:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Sep 11 14:34:52 brilp0017 dockerd[2380]: time="2020-09-11T14:34:52.864254519+01:00" level=info msg="Attempting next endpoint for pull after error: failed to register layer: Error processing tar file(exit status 1): Error cleaning up after pivot: remove /.pivot_root534731447: device or resource busy"
After this the error remains the same even after stopping and starting docker service multiple times with systemctl. After restarting the laptop fully and starting the docker service it starts work as expected until the next time docker pull command is used.
I have searched for solution on the internet but majority of them point to the user not being in docker group but that is not the case for me;
[desai#brilp0017 ~]$ groups
sys network power vboxusers wireshark sambashare docker lp wheel desai
Here is the output of docker version before it crashes for version details;
[desai#brilp0017 ~]$ docker version
Client:
Version: 19.03.12-ce
API version: 1.40
Go version: go1.14.5
Git commit: 48a66213fe
Built: Sat Jul 18 01:33:21 2020
OS/Arch: linux/amd64
Experimental: false
Server:
Engine:
Version: 19.03.12-ce
API version: 1.40 (minimum version 1.12)
Go version: go1.14.5
Git commit: 48a66213fe
Built: Sat Jul 18 01:32:59 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.4.0.m
GitCommit: 09814d48d50816305a8e6c1a4ae3e2bcc4ba725a.m
runc:
Version: 1.0.0-rc92
GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version: 0.18.0
GitCommit: fec3683
I am using Manjaro linux OS;
Operating System: Manjaro Linux
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 4.19.141-2-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU # 1.80GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Any help on this would be appreciated.
This issue was resolved by updating the kernel to 5.4 version.

Docker container start issue

I am trying to start docker containers, Seems like it has failed. After Analyzing DockerD logs.
ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 13 21:37:58 ubuntu-nuc2 dockerd[692]: time="2020-03-13T21:37:58.277230495Z" level=error msg="stream copy error: reading from a closed fifo"
Mar 13 21:37:58 ubuntu-nuc2 dockerd[692]: time="2020-03-13T21:37:58.277625568Z" level=error msg="stream copy error: reading from a closed fifo"
Mar 13 21:37:58 ubuntu-nuc2 dockerd[692]: time="2020-03-13T21:37:58.364681832Z" level=error msg="54dd3a9bfcbcbcdddcc82350e8045985d8c8495ac465e7e335c3a91b75bdf30b cleanup: failed to delete container from containerd: no such container"
Mar 13 21:37:58 ubuntu-nuc2 dockerd[692]: time="2020-03-13T21:37:58.364824367Z" level=error msg="Handler for POST /v1.25/containers/54dd3a9bfcbcbcdddcc82350e8045985d8c8495ac465e7e335c3a91b75bdf30b/start returned error: OCI runtime create failed: container_linux.go:349: starting container process caused \"process_linux.go:449: container init caused \\\"rootfs_linux.go:109: jailing process inside rootfs caused \\\\\\\"pivot_root invalid argument\\\\\\\"\\\"\": unknown"
Mar 13 21:37:59 ubuntu-nuc2 dockerd[692]: time="2020-03-13T21:37:59.159258456Z" level=error msg="8292a9a1eb9fccfe8848c57f3aaaf2c52c557c5b55b606112cdf66148fbba6d7 cleanup: failed to delete container from containerd: no such container"
Mar 13 21:37:59 ubuntu-nuc2 dockerd[692]: time="2020-03-13T21:37:59.159376298Z" level=error msg="Handler for POST /v1.25/containers/8292a9a1eb9fccfe8848c57f3aaaf2c52c557c5b55b606112cdf66148fbba6d7/start returned error: cgroups: cgroup mountpoint does not exist: unknown"
Mar 13 22:14:22 ubuntu-nuc2 dockerd[692]: time="2020-03-13T22:14:22.094213684Z" level=error msg="Error setting up exec command in container rwo_gluster-server_1: Container 54dd3a9bfcbcbcdddcc82350e8045985d8c8495ac465e7e335c3a91b75bdf30b is not running"
-- Reboot --
Mar 13 22:24:23 ubuntu-nuc2 systemd[1]: Starting Docker Application Container Engine...
I went through several threads for help and got this.
export DOCKER_RAMDISK=true
But not able to figure out what is happening, Why Containers failed due to pivot_root error?
Docker-compose.yml:
gluster-server:
image: edge/glusterfs-rest:7
entrypoint: dumb-init glusterd --no-daemon --pid-file=/var/run/glusterd.pid
restart: unless-stopped
privileged: true
ipc: host
network_mode: host
# pid: host
userns_mode: host
volumes:
- gluster_database_vol:/var/lib/glusterd
- docker_pid_vol:/var/run
- /mnt:/mnt:shared
- /dev:/dev
- /opt:/opt
- /sys/fs/cgroup:/sys/fs/cgroup:ro
- /var/log/glusterfs:/var/log/glusterfs:shared
- /etc/ssl:/etc/ssl
depends_on:
- app-docker
- gluster-rest
- gluster-security-enabler

'overlay2' is not supported over nfs" storage-driver=overlay2

when I am start docker(version 18.09.6) using:
service docker start
the log output:
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058391699+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420166a80, READY" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.065016392+08:00" level=error msg="'overlay2' is not supported over nfs" storage-driver=overlay2
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: Error starting daemon: error initializing graphdriver: backing file system is unsupported for this graph driver
this is my deamon.json config:
{
"data-root": "/data/docker/lib/docker",
"storage-driver": "overlay2",
"storage-opts": [
"overlay2.override_kernel_check=true",
"overlay2.size=1G"
]
}
what is problem with my docker? this is the full log output:
Sep 14 23:47:23 iZuf63refzweg1d9dh94t9Z systemd[1]: Starting Docker Application Container Engine...
Sep 14 23:47:23 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:23+08:00" level=warning msg="The \"-g / --graph\" flag is deprecated. Please use \"--data-root\" instead"
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.054488483+08:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.054528530+08:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.054680027+08:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0 <nil>}]" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.054720022+08:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.054796786+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420166680, CONNECTING" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.055020881+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420166680, READY" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058007723+08:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058029632+08:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058172958+08:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0 <nil>}]" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058204756+08:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058254343+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420166a80, CONNECTING" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.058391699+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420166a80, READY" module=grpc
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: time="2019-09-14T23:47:24.065016392+08:00" level=error msg="'overlay2' is not supported over nfs" storage-driver=overlay2
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z dockerd[21199]: Error starting daemon: error initializing graphdriver: backing file system is unsupported for this graph driver
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z systemd[1]: Failed to start Docker Application Container Engine.
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z systemd[1]: Unit docker.service entered failed state.
Sep 14 23:47:24 iZuf63refzweg1d9dh94t9Z systemd[1]: docker.service failed.
Sep 14 23:47:26 iZuf63refzweg1d9dh94t9Z systemd[1]: docker.service holdoff time over, scheduling restart.
Sep 14 23:47:26 iZuf63refzweg1d9dh94t9Z systemd[1]: Stopped Docker Application Container Engine.
Sep 14 23:47:26 iZuf63refzweg1d9dh94t9Z systemd[1]: start request repeated too quickly for docker.service
Sep 14 23:47:26 iZuf63refzweg1d9dh94t9Z systemd[1]: Failed to start Docker Application Container Engine.
Sep 14 23:47:26 iZuf63refzweg1d9dh94t9Z systemd[1]: Unit docker.service entered failed state.
Sep 14 23:47:26 iZuf63refzweg1d9dh94t9Z systemd[1]: docker.service failed.
The point is my host(total 5) mount a share nfs disk.Change the path should solve the problem.
[root#iZuf63refzweg1dh94t9Z containers]# df -T /data
Filesystem Type 1K-blocks Used Available Use% Mounted on
3761b-lrf18.cn-shanghai.nas.aliyuncs.com:/ nfs4 10995116277760 233244672 10994883033088 1% /data
change the daemon.json root path to local:
{
"data-root": "/var/lib/docker",
"storage-driver": "overlay2"
}

centos 7 server keeps restarting while building the docker images

I have docker installed on centos & system.
I am able to download docker images using docker pull command.
but when I run the container using docker run alpine, the server restarts.
this is happening every time.
I found this from /var/log/messages | grep docker
CODE
Below is my configuration:
$ docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 18.09.0
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 local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-957.1.3.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 40
Total Memory: 251.7GiB
Name: CHMCISPRDOCKENG
ID: XFPC:SYGF:Q3P7:M32Z:VRTX:TFGZ:YA43:NYSY:UGVK:PC2M:HVAU:TIM2
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:
some-registry
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
WARNING: API is accessible on http://127.0.0.1:2375 without encryption.
Access to the remote API is equivalent to root access on the host. Refer
to the 'Docker daemon attack surface' section in the documentation for
more information:
https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Now when I run docker pull alpine. image is downloaded successfully.
But when I run docker run -it alpine , I am logged out from the server & server is restarted.
below are the logs when I ran cat /var/log/messages | grep docker.
Dec 17 19:28:12 CHMCISPRDOCKENG systemd: Started docker.service.
Dec 17 19:28:12 CHMCISPRDOCKENG audispd: node=CHMCISPRDOCKENG type=SERVICE_START msg=audit(1545055092.725:167): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.023820157+05:30" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting --tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]"
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.043715041+05:30" level=info msg="libcontainerd: started new containerd process" pid=15564
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.043788743+05:30" level=info msg="parsed scheme: \"unix\"" module=grpc
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.043810434+05:30" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.044206037+05:30" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0 <nil>}]" module=grpc
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.044227097+05:30" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.044283337+05:30" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420963f00, CONNECTING" module=grpc
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.726282962+05:30" level=info msg="starting containerd" revision=c4446665cb9c30056f4998ed953e6d4ff22c7c39 version=1.2.0
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.727202682+05:30" level=info msg="loading plugin "io.containerd.content.v1.content"..." type=io.containerd.content.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.733393760+05:30" level=info msg="loading plugin "io.containerd.snapshotter.v1.btrfs"..." type=io.containerd.snapshotter.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.733593273+05:30" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.btrfs" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter"
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.733607841+05:30" level=info msg="loading plugin "io.containerd.snapshotter.v1.aufs"..." type=io.containerd.snapshotter.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.737142848+05:30" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.aufs" error="modprobe aufs failed: "modprobe: FATAL: Module aufs not found.\n": exit status 1"
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.737165057+05:30" level=info msg="loading plugin "io.containerd.snapshotter.v1.native"..." type=io.containerd.snapshotter.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.740458140+05:30" level=info msg="loading plugin "io.containerd.snapshotter.v1.overlayfs"..." type=io.containerd.snapshotter.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.747800098+05:30" level=info msg="loading plugin "io.containerd.snapshotter.v1.zfs"..." type=io.containerd.snapshotter.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.748343654+05:30" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.zfs" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter"
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.748359281+05:30" level=info msg="loading plugin "io.containerd.metadata.v1.bolt"..." type=io.containerd.metadata.v1
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.748378883+05:30" level=warning msg="could not use snapshotter zfs in metadata plugin" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter"
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.748386577+05:30" level=warning msg="could not use snapshotter btrfs in metadata plugin" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter"
Dec 17 19:28:16 CHMCISPRDOCKENG dockerd: time="2018-12-17T19:28:16.748392893+05:30" level=warning msg="could not use snapshotter aufs in metadata plugin" error="modprobe aufs failed: "modprobe: FATAL: Module aufs not found.\n": exit status 1"
Any suggestions?
Found the answer to be storage driver problem.
the configuration of the server was not supporting the default overlay2 storage driver for docker. changing it to devicemapper fixed things.

Unable to run docker-compose

Following this article on Jhipster, I build the project. I, however, can't run docker-compose. So, I try to figure out the problem. I walk step by step with this Docker-Compose article without luck.
$ sudo service docker status
docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-12-27 15:40:22 PST; 2 days ago
Docs: https://docs.docker.com
Main PID: 1960 (dockerd)
Tasks: 20 (limit: 4440)
Memory: 68.2M
CGroup: /system.slice/docker.service
├─1960 /usr/bin/dockerd -H fd://
└─2093 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --s
Dec 27 15:40:10 tk-PC dockerd[1960]: time="2018-12-27T15:40:10.493340278-08:00" level=warning msg="Your kernel does not support swap memory li
Dec 27 15:40:10 tk-PC dockerd[1960]: time="2018-12-27T15:40:10.493612101-08:00" level=warning msg="Your kernel does not support cgroup rt peri
Dec 27 15:40:10 tk-PC dockerd[1960]: time="2018-12-27T15:40:10.493681034-08:00" level=warning msg="Your kernel does not support cgroup rt runt
Dec 27 15:40:10 tk-PC dockerd[1960]: time="2018-12-27T15:40:10.496381656-08:00" level=info msg="Loading containers: start."
Dec 27 15:40:17 tk-PC dockerd[1960]: time="2018-12-27T15:40:17.498415923-08:00" level=info msg="Default bridge (docker0) is assigned with an I
Dec 27 15:40:19 tk-PC dockerd[1960]: time="2018-12-27T15:40:19.646853084-08:00" level=info msg="Loading containers: done."
Dec 27 15:40:22 tk-PC dockerd[1960]: time="2018-12-27T15:40:22.512083092-08:00" level=info msg="Daemon has completed initialization"
Dec 27 15:40:22 tk-PC dockerd[1960]: time="2018-12-27T15:40:22.512266914-08:00" level=info msg="Docker daemon" commit=89658be graphdriver=aufs
Dec 27 15:40:22 tk-PC dockerd[1960]: time="2018-12-27T15:40:22.553322342-08:00" level=info msg="API listen on /var/run/docker.sock"
Dec 27 15:40:22 tk-PC systemd[1]: Started Docker Application Container Engine.
$ sudo ls -la /var/run/docker.sock
srw-rw---- 1 root docker 0 Dec 27 15:39 /var/run/docker.sock
$ sudo usermod -aG docker ${USER}
$ docker-compose -f docker-compose.yml build --build-arg UID=$(id -u)
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
The result of the last step is the same as "docker-compose up -d". According to the article, it would be a permission problem if the problem still exists at this point. How can I find what permission issue?
There are multiple ways you can solve this problem. Firstly try to export environment variable of docker host with command:
export DOCKER_HOST=/var/run/docker.sock
If it works you can add the same line to your bashrc config to save this export permanently.
If it doesn't work you can try to modify docker daemon config. It located in
/etc/docker/daemon.json
You'll need to append the localhost to your hosts like that:
"hosts": ["old_hosts_not_modified_only_append_new_one", "tcp://localhost:2376"],
and restart docker daemon using command:
service docker restart
Hope it gonna help ya

Resources