Share and learn in the Docker community.
Hi guys,
I have a question related to docker service.
I didn’t install docker-engine but docker contained when installing kubernetes as i followed this tutorial.
I checked the docker’s version and it was 1.8…2.
But when i start the docker, this error appeared:
"Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details."
Can you guys tell me why?
if you run systemctl status docker.service you will get the logs and it might be more clear what the problem is. other wise this is way to vague to give you any help.
Always the same error: Independencies for job kubelet.service. Could you give the above-meantioned a try because i did many times and still failed.
Could you please post the full message output from systemctl status docker.service and journalctl -xe as i need more detail to help you out.
This is error when i started docker.service.
[root@ip-10-0-7-223 ~]# systemctl start docker.service
Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.
And what happend when check status of docker.service.
[root@ip-10-0-7-223 ~]# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: inactive (dead) (Result: exit-code) since Tue 2016-02-09 02:39:40 UTC; 23s ago
Docs: http://docs.docker.com
Process: 32085 ExecStart=/usr/bin/docker daemon $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY (code=exited, status=2)
Main PID: 32085 (code=exited, status=2)
CGroup: /system.slice/docker.service
Feb 09 02:39:40 ip-10-0-7-223 systemd[1]: docker.service: main process exite…T
Feb 09 02:39:40 ip-10-0-7-223 systemd[1]: Failed to start Docker Application…
Feb 09 02:39:40 ip-10-0-7-223 systemd[1]: Unit docker.service entered failed…
Feb 09 02:39:40 ip-10-0-7-223 systemd[1]: docker.service failed.
Feb 09 02:39:40 ip-10-0-7-223 systemd[1]: docker.service holdoff time over, …
Hint: Some lines were ellipsized, use -l to show in full.
– Unit polkit.service has begun starting up.
Feb 09 02:35:21 ip-10-0-7-223 polkitd[31731]: Started polkitd version 0.112
Feb 09 02:35:21 ip-10-0-7-223 polkitd[31731]: Loading rules from directory /etc/polkit-1/rules.d
Feb 09 02:35:21 ip-10-0-7-223 polkitd[31731]: Loading rules from directory /usr/share/polkit-1/rules.d
Feb 09 02:35:21 ip-10-0-7-223 polkitd[31731]: Finished loading, compiling and executing 2 rules
Feb 09 02:35:21 ip-10-0-7-223 dbus[497]: [system] Successfully activated service 'org.freedesktop.PolicyKit1’
Feb 09 02:35:21 ip-10-0-7-223 polkitd[31731]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Feb 09 02:35:21 ip-10-0-7-223 systemd[1]: Started Authorization Manager.
– Subject: Unit polkit.service has finished start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[root@ip-10-0-7-223 ~]#
[root@ip-10-0-7-223 ~]# clear
– Unit docker-storage-setup.service has begun starting up.
Feb 09 02:41:33 ip-10-0-7-223 docker-storage-setup[32132]: Volume group “xvda1” not found
Feb 09 02:41:33 ip-10-0-7-223 docker-storage-setup[32132]: Cannot process volume group xvda1
Feb 09 02:42:33 ip-10-0-7-223 systemd-udevd[10877]: worker [32131] /devices/virtual/block/dm-1 is taking a long time
So think this could be your problem.
Feb 09 02:37:13 ip-10-0-7-223 docker-storage-setup[32021]: Volume group "xvda1" not found
Feb 09 02:37:13 ip-10-0-7-223 docker-storage-setup[32021]: Cannot process volume group xvda1
Feb 09 02:37:13 ip-10-0-7-223 docker-storage-setup[32021]: No volume group has been specified and root device volume group could not be determined. Exiting
Feb 09 02:37:13 ip-10-0-7-223 systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE
So it looks like you set up the storage incorrectly or made a typo maybe in the docker config, which set up instructions did you follow to set up the docker agent?
Just as i said in my first post,my intention was create a Kubernets cluster which is used to deploy and manager Docker container. You can see the link of tutorial i followed in my first post.
The point is i failed all the time when following that tutorial, so i think maybe it’s related to docker or sth.
Kubernetes packages contained docker package so i didn’t have to use some command line: yum install docker-engine…etc
So i checked the docker status and found out it was UNACTIVE. Then i tried to started docker service but it didn’t work. That’s all it is.
Anyone know about this?
I got almost the same, because I have upgraded Kernel version.
(from 4.4.0 to 4.7.1)
Reverting Kernel to 4.4.0 is how I fixed the problem.
jiapei@jiapei-GT72-6QE:~$ systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Wed 2017-12-20 13:46:17 CST; 16min ago
Docs: https://docs.docker.com
Process: 26890 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
Main PID: 26890 (code=exited, status=1/FAILURE)Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: Failed to start Docker Application Container Engine.
Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: docker.service: Unit entered failed state.
Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: docker.service: Failed with result ‘exit-code’.
Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: Stopped Docker Application Container Engine.
Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: docker.service: Start request repeated too quickly.
Dec 20 13:46:17 jiapei-GT72-6QE systemd[1]: Failed to start Docker Application Container Engine.
jiapei@jiapei-GT72-6QE:~$ journalctl -xe
Dec 20 13:56:25 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:25 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:26 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:26 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:28 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: wlp2s0: SME: Trying to authenticate with 14:dd:a9:1a:cf:e0 (SSID=‘SHAW-657502-5G’ freq=5200 MHz)
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: authenticate with 14:dd:a9:1a:cf:e0
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: send auth to 14:dd:a9:1a:cf:e0 (try 1/3)
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: authenticated
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: wlp2s0: Trying to associate with 14:dd:a9:1a:cf:e0 (SSID=‘SHAW-657502-5G’ freq=5200 MHz)
Dec 20 13:56:29 jiapei-GT72-6QE NetworkManager[959]: [1513749389.8032] device (wlp2s0): supplicant interface state: scanning → authenticating
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: wlp2s0: Associated with 14:dd:a9:1a:cf:e0
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: associate with 14:dd:a9:1a:cf:e0 (try 1/3)
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: RX AssocResp from 14:dd:a9:1a:cf:e0 (capab=0x411 status=0 aid=1)
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: associated
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: p2p-dev-wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: EEPROM regdomain: 0x8348
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: EEPROM indicates we should expect a country code
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: doing EEPROM country->regdmn map search
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: country maps to regdmn code: 0x3a
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: Country alpha2 being used: US
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: Regpair used: 0x3a
Dec 20 13:56:29 jiapei-GT72-6QE kernel: ath: regdomain 0x8348 dynamically updated by country IE
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: wlp2s0: WPA: Key negotiation completed with 14:dd:a9:1a:cf:e0 [PTK=CCMP GTK=TKIP]
Dec 20 13:56:29 jiapei-GT72-6QE wpa_supplicant[1281]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 14:dd:a9:1a:cf:e0 completed [id=0 id_str=]
Dec 20 13:56:29 jiapei-GT72-6QE NetworkManager[959]: [1513749389.8206] device (wlp2s0): supplicant interface state: authenticating → associating
Dec 20 13:56:29 jiapei-GT72-6QE NetworkManager[959]: [1513749389.8234] device (wlp2s0): supplicant interface state: associating → completed
Dec 20 13:56:29 jiapei-GT72-6QE kernel: wlp2s0: Limiting TX power to 14 (17 - 3) dBm as advertised by 14:dd:a9:1a:cf:e0
Dec 20 14:00:01 jiapei-GT72-6QE CRON[27528]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 20 14:00:01 jiapei-GT72-6QE CRON[27527]: pam_unix(cron:session): session opened for user smmsp by (uid=0)
Dec 20 14:00:01 jiapei-GT72-6QE CRON[27529]: (root) CMD ( test -x /usr/sbin/tigercron && { [ -r “$DEFAULT” ] && . “$DEFAULT” ; nice -n$NICETIGER /usr/sbin/tigercron -q ; })
Dec 20 14:00:01 jiapei-GT72-6QE CRON[27530]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share
Dec 20 14:00:01 jiapei-GT72-6QE sm-msp-queue[27586]: My unqualified host name (jiapei-GT72-6QE) unknown; sleeping for retry
Dec 20 14:00:04 jiapei-GT72-6QE sendmail[27859]: My unqualified host name (jiapei-GT72-6QE) unknown; sleeping for retry
Dec 20 14:01:01 jiapei-GT72-6QE sm-msp-queue[27586]: unable to qualify my own domain name (jiapei-GT72-6QE) – using short name
Dec 20 14:01:01 jiapei-GT72-6QE CRON[27527]: pam_unix(cron:session): session closed for user smmsp
Dec 20 14:01:04 jiapei-GT72-6QE sendmail[27859]: unable to qualify my own domain name (jiapei-GT72-6QE) – using short name
Dec 20 14:01:04 jiapei-GT72-6QE sendmail[27859]: vBK6142b027859: from=root, size=651, class=0, nrcpts=1, msgid=201712200601.vBK6142b027859@jiapei-GT72-6QE, relay=root@localho
Dec 20 14:01:05 jiapei-GT72-6QE sm-mta[27891]: vBK614DW027891: from=root@jiapei-GT72-6QE, size=899, class=0, nrcpts=1, msgid=201712200601.vBK6142b027859@jiapei-GT72-6QE, pr
Dec 20 14:01:05 jiapei-GT72-6QE sendmail[27859]: vBK6142b027859: to=root, ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30651, relay=[127.0.0.1] [127.0
Dec 20 14:01:05 jiapei-GT72-6QE CRON[27528]: pam_unix(cron:session): session closed for user root
Dec 20 14:01:05 jiapei-GT72-6QE sm-mta[27892]: vBK614DW027891: to=root@jiapei-GT72-6QE, ctladdr=root@jiapei-GT72-6QE (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pjiapei@jiapei-GT72-6QE:~$