Q: Kubernetes Install on CoreOS showing Dependency failed for Docker Application Container Engine

2
votes

Dependency failed for Docker Application Container Engine. May 20 13:06:52 localhost systemd[1]: docker.service: Job docker.service/start failed with result 'dependency' when I do a systemctl status docker.

Using the CoreOS install documentation, Kubelet(master) all on same node.

Where would I start looking to debug this from?

1
kubernetescoreos
core@localhost ~/bin $ sudo systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib64/systemd/system/docker.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/docker.service.d └─40-flannel.conf Active: inactive (dead) Docs: docs.docker.com – Gazzer
It looks like flannel didn't start? I'm not totally clear. journalctl will give you log output of these apps, that should get you started. – Andy Smith
Thanks Andy! When I do a core@localhost /bin $ systemctl status flannel ● flannel.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) core@localhost /etc/systemd/system/docker.service.d $ cat 40-flannel.conf [Unit] Requires=flanneld.service After=flanneld.service Yet - Core@localhost /bin $ sudo systemctl start flannel Failed to start flannel.service: Unit flannel.service failed to load: No such file or directory. – Gazzer
And what about journalctl? It's kind of difficult to read what your'e pasting – Andy Smith
The service name is flanneld, not flannel. – Sahand Hariri

1 Answers

3
votes

I know it's a little late, but I think you need to ensure flanneld.service service is running. If you're following the CoreOS step-by-step documentation for building a Kubernetes cluster with CoreOS, then flanneld is a dependency for the docker engine.

If you made a systemd drop-in replacement in /etc/systemd/system/docker.service.d/40-flannel.conf, then that is most likely the case as evidenced here:

[Unit] Requires=flanneld.service After=flanneld.service