i m new to docker
i have gone through multible bloges regarding installing docker on CentOS7 , i m currently running my deployment using VMware virtual machine.
i do have a automated successful deployment via vRealize Automation where i do a yum -y update, disable and stop the firewalld service and install and start the latest docker service 1.9 i think . but it seems the docker daemon isnt running after all that
for example if i do docker pull centos i get the follwoing error :
[root@vRA-VM-123 ~]# docker pull centos
Using default tag: latest
Post http:///var/run/docker.sock/v1.20/images/create?fromImage=centos%3Alatest: read unix /var/run/docker.sock: connection reset by peer.
- Are you trying to connect to a TLS-enabled daemon without TLS?
- Is your docker daemon up and running?
[root@vRA-VM-123 ~]# docker daemon
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
ERRO[0060] WARNING: No --storage-opt dm.thinpooldev specified, using loopback; this configuration is strongly discouraged for production use
ERRO[0224] [graphdriver] prior storage driver “devicemapper” failed: exit status 1
FATA[0224] Error starting daemon: error initializing graphdriver: exit status 1
[root@vRA-VM-123 ~]#
i was wondering if i m doing anything wrong or missing any steps any help is appreciated
also Here the output for : journalctl -xe for more information
– Logs begin at Thu 2016-01-28 01:51:36 EST, end at Thu 2016-01-28 09:46:54 EST. –
Jan 28 07:59:32 vRA-VM-123.vmwarelab.local systemd[1]: Unit docker-storage-setup.service entered failed state.
Jan 28 07:59:32 vRA-VM-123.vmwarelab.local systemd[1]: docker-storage-setup.service failed.
Jan 28 07:59:32 vRA-VM-123.vmwarelab.local systemd[1]: Starting Docker Application Container Engine…
– Subject: Unit docker.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker.service has begun starting up.
Jan 28 07:59:32 vRA-VM-123.vmwarelab.local docker[25747]: time=“2016-01-28T07:59:32.449316146-05:00” level=error msg="WARNING: No --storage-opt dm.thinpooldev specified, using loopback; this configuration is strongly discouraged for production use"
Jan 28 07:59:32 vRA-VM-123.vmwarelab.local docker[25747]: time=“2016-01-28T07:59:32.456402508-05:00” level=info msg="Listening for HTTP on unix (/var/run/docker.sock)"
Jan 28 07:59:35 vRA-VM-123.vmwarelab.local systemd-udevd[25754]: inotify_add_watch(7, /dev/dm-4, 10) failed: No such file or directory
Jan 28 07:59:35 vRA-VM-123.vmwarelab.local systemd-udevd[483]: error: /dev/dm-4: No such file or directory
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: docker.service start operation timed out. Terminating.
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: docker.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: h ttp://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker.service has failed.
– The result is failed.
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: Unit docker.service entered failed state.
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: docker.service failed.
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: docker.service holdoff time over, scheduling restart.
Jan 28 08:00:32 vRA-VM-123.vmwarelab.local systemd[1]: Starting Docker Storage Setup…
– Subject: Unit docker-storage-setup.service has begun start-up
– Defined-By: systemd
– Support: h ttp://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker-storage-setup.service has begun starting up.
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local systemd[1]: Started Session 16 of user root.
– Subject: Unit session-16.scope has finished start-up
– Defined-By: systemd
– Support: h ttp://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit session-16.scope has finished starting up.
– The start-up result is done.
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local systemd[1]: Starting Session 16 of user root.
– Subject: Unit session-16.scope has begun start-up
– Defined-By: systemd
– Support: h ttp://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit session-16.scope has begun starting up.
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local CROND[25778]: (root) CMD (run-parts /etc/cron.hourly)
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local run-parts(/etc/cron.hourly)[25781]: starting 0anacron
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local run-parts(/etc/cron.hourly)[25787]: finished 0anacron
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local run-parts(/etc/cron.hourly)[25789]: starting 0yum-hourly.cron
Jan 28 08:01:01 vRA-VM-123.vmwarelab.local run-parts(/etc/cron.hourly)[25793]: finished 0yum-hourly.cron
Jan 28 08:01:32 vRA-VM-123.vmwarelab.local systemd-udevd[483]: worker [25764] /devices/virtual/block/dm-4 is taking a long time
Jan 28 08:01:56 vRA-VM-123.vmwarelab.local docker-storage-setup[25765]: Metadata volume docker-poolmeta already exists. Not creating a new one.
Jan 28 08:01:56 vRA-VM-123.vmwarelab.local docker-storage-setup[25765]: There is not enough free space in volume group centos to create data volume of size MIN_DATA_SIZE=2G.
Jan 28 08:01:56 vRA-VM-123.vmwarelab.local systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE