docker 操作响应缓慢甚至timeout有什么可能的原因?


env:

[root@h63 ~]# docker info
Containers: 26
Images: 581
Storage Driver: devicemapper
Pool Name: docker-253:5-134300935-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 23.11 GB
Data Space Total: 107.4 GB
Data Space Available: 84.26 GB
Metadata Space Used: 29.21 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.118 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.10.0-229.14.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 4
Total Memory: 7.64 GiB
Name: h63.localdomain
ID: TFZE:7L6P:C3Q3:YFIP:MSOE:4MOV:WNWZ:KWYN:BMVC:ORJ4:UZZ3:4AJM
已邀请:

zlcolin

赞同来自:


Storage Driver: devicemapper 性能很差吗?

zlcolin

赞同来自:


又死机了,重起后 docker不能启动

● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since 五 2016-03-04 12:01:19 CST; 14s ago
Docs: http://docs.docker.com
Process: 3586 ExecStart=/usr/bin/docker -d $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=1/FAILURE)
Main PID: 3586 (code=exited, status=1/FAILURE)

3月 04 12:01:19 h63.localdomain systemd[1]: Starting Docker Application Container Engine...
3月 04 12:01:19 h63.localdomain docker[3586]: time="2016-03-04T12:01:19.050449679+08:00" level=info msg="Listening for HTTP on unix (/var/run/docker.sock)"
3月 04 12:01:19 h63.localdomain docker[3586]: time="2016-03-04T12:01:19.053569445+08:00" level=warning msg="--storage-opt dm.thinpooldev is preferred over --storage-opt dm.datadev or dm.metadatadev"
3月 04 12:01:19 h63.localdomain docker[3586]: time="2016-03-04T12:01:19.089962029+08:00" level=error msg="[graphdriver] prior storage driver \"devicemapper\" failed: Base Device UUID verification failed. Possibly using a different thin pool then last invocation:Error running DeviceCreate (ActivateDevice) dm_task_run failed"
3月 04 12:01:19 h63.localdomain docker[3586]: time="2016-03-04T12:01:19.090058930+08:00" level=fatal msg="Error starting daemon: error initializing graphdriver: Base Device UUID verification failed. Possibly using a different thin pool then last invocation:Error running DeviceCreate (ActivateDevice) dm_task_run failed"
3月 04 12:01:19 h63.localdomain systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
3月 04 12:01:19 h63.localdomain systemd[1]: Failed to start Docker Application Container Engine.
3月 04 12:01:19 h63.localdomain systemd[1]: Unit docker.service entered failed state.

3月 04 12:01:19 h63.localdomain systemd[1]: docker.service failed.

- [root@h63 ~]# docker version
Client version: 1.7.1
Client API version: 1.19
Package Version (client): docker-1.7.1-115.el7.x86_64
Go version (client): go1.4.2
Git commit (client): 446ad9b/1.7.1
OS/Arch (client): linux/amd64
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

zlcolin

赞同来自:


docker-compose up -d

ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

zlcolin

赞同来自:


up, anyone encounter this issue please?

要回复问题请先登录注册