docker failed to start using gluster volume

eskuai commented 4 years ago

Problem description

I am trying to start 3 docker process into 3 differents machines, using a gluster volume as graph directory

There is a gluster volume, named "registry", and it is mounted in three machines

mount -t glusterfs -obackup-volfile-servers=worker-node7-gfs:worker-node8-gfs worker-node6-gfs:/registry /registryMaster

The daemon file template into 3 machines, is:

{
  "insecure-registries" : ["k8s-reg-IDMACHINE:5000"],
  "graph": "/registryMaster",
  "storage-driver": "devicemapper"
}

Problem location

Docker doesn't start, shows

- Unit docker.service has begun starting up.
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18Z" level=warning msg="The \"graph\" config file option is deprecated. Please use \"data-root\" instead."
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.965852542Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.965880033Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.966041875Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]" mod
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.966069955Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.966126206Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc4200450f0, CONNECTING" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.966337750Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc4200450f0, READY" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.970419400Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.970447410Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.970987788Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]" mod
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.971013449Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.971054869Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc4200453e0, CONNECTING" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.971194142Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc4200453e0, READY" module=grpc
Nov 14 11:50:18 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:18.974919207Z" level=warning msg="[graphdriver] WARNING: the devicemapper storage-driver is deprecated, and will be removed in a future
Nov 14 11:50:19 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:19.013003623Z" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.th
Nov 14 11:50:19 k8s-squid3-c-pub dockerd[30918]: time="2019-11-14T11:50:19.033466356Z" level=warning msg="Base device already exists and has filesystem xfs on it. User specified filesystem  will be ignored."
Nov 14 11:50:20 k8s-squid3-c-pub dockerd[30918]: Error starting daemon: error while opening volume store metadata database: timeout
Nov 14 11:50:20 k8s-squid3-c-pub systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Nov 14 11:50:20 k8s-squid3-c-pub systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd

Project version(s) affected

Client: Version: 18.09.2 API version: 1.39 Go version: go1.10.6 Git commit: 6247962 Built: Sun Feb 10 04:13:27 2019 OS/Arch: linux/amd64 Experimental: false

Server: Docker Engine - Community Engine: Version: 18.09.2 API version: 1.39 (minimum version 1.12) Go version: go1.10.6 Git commit: 6247962 Built: Sun Feb 10 03:47:25 2019 OS/Arch: linux/amd64 Experimental: false

traci-morrison commented 4 years ago

Thank you for your feedback. However, it looks like your issue is not about Docker documentation, but that you may be having trouble with Docker itself. Please file a Docker support ticket or check out https://forums.docker.com/ to see if you can find a solution.

If this really is a documentation issue and I have misunderstood,please reopen it with more information.

docker-robott commented 1 year ago

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

docker / docs