I am getting following error on systemctl start docker.
Apart from the failure in executing daemon, it is filling up entire local drive.
[root@paravance-18 ~]# journalctl -xe
– Subject: A new session 2 has been created for user root
– Defined-By: systemd
– Support: http:// lists.freedesktop.org/mailman/listinfo/systemd-devel
– Documentation: http:/ /www.freedesktop.org/wiki/Software/systemd/multiseat
– A new session with the ID 2 has been created for the user root.
– The leading process of the session is 1500.
Aug 19 13:10:07 paravance-18 systemd[1]: Started Session 2 of user root.
– Subject: Unit session-2.scope has finished start-up
– Defined-By: systemd
– Support: http:// lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit session-2.scope has finished starting up.
– The start-up result is done.
Aug 19 13:10:07 paravance-18 sshd[1500]: pam_unix(sshd:session): session opened for user root by (uid=0)
Aug 19 13:11:16 paravance-18 NetworkManager[709]: Connectivity check for uri ‘https://fedoraproject.org/static/hotspot.txt’ failed with ‘Could not connect: Network is unreachable’.
Aug 19 13:14:10 paravance-18 systemd[1]: Reloading.
Aug 19 13:14:10 paravance-18 systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictio
Aug 19 13:14:11 paravance-18 systemd[1]: Unknown serialization item 'subscribed=:1.1’
Aug 19 13:14:11 paravance-18 systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 19 13:14:11 paravance-18 groupadd[1638]: group added to /etc/group: name=docker, GID=977
Aug 19 13:14:11 paravance-18 groupadd[1638]: group added to /etc/gshadow: name=docker
Aug 19 13:14:11 paravance-18 groupadd[1638]: new group: name=docker, GID=977
Aug 19 13:14:11 paravance-18 yum[1592]: Installed: docker-engine-1.8.1-1.fc21.x86_64
Aug 19 13:14:49 paravance-18 systemd[1]: Starting Docker Socket for the API.
– Subject: Unit docker.socket has begun with start-up
– Defined-By: systemd
– Support: http:// lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker.socket has begun starting up.
Aug 19 13:14:49 paravance-18 systemd[1]: Listening on Docker Socket for the API.
– Subject: Unit docker.socket has finished start-up
– Defined-By: systemd
– Support: http:/ /lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker.socket has finished starting up.
– The start-up result is done.
Aug 19 13:14:49 paravance-18 systemd[1]: Starting Docker Application Container Engine…
– Subject: Unit docker.service has begun with start-up
– Defined-By: systemd
– Support: http://l ists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker.service has begun starting up.
Aug 19 13:14:49 paravance-18 systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Aug 19 13:14:49 paravance-18 kernel: loop: module loaded
Aug 19 13:15:05 paravance-18 docker[1658]: time=“2015-08-19T13:15:05.207633298+02:00” level=fatal msg="Error starting daemon: error initializing graphdriver: exit status 1"
Aug 19 13:15:05 paravance-18 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Aug 19 13:15:05 paravance-18 systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: http: //lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit docker.service has failed.
– The result is failed.
Aug 19 13:15:05 paravance-18 systemd[1]: Unit docker.service entered failed state.
Aug 19 13:15:05 paravance-18 systemd[1]: docker.service failed.