English
« Back to projectatomic.io
Ask Your Question
0

getting started guide no flannel no docker interface

asked 2016-05-11 21:43:22 +0000

silemmo gravatar image

Hello evreybody, I haver tried to do the guide but I have a problem. At the part "Confirm network configuration and cluster health" , docker and flannel are inactive or dead and "ip a" doesnt show docker0 or flannel.1

I followed the guide very carefully so I dont understand what is the problem ?

If someon can help me it will be awesome.

edit retag flag offensive close merge delete

Comments

If there's no flannel interface then flannel didn't start, there should be an error in the system journal. Can you find that error and paste it here? I'd expect that docker is showing a dependency failure in the journal as well.

nzwulfin ( 2016-05-16 20:03:53 +0000 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2016-05-17 20:30:55 +0000

silemmo gravatar image

I am not sure how to look at the system journal there is a lot of stuff when i type sudo journalctl, but here it's my status.

[vagrant@localhost ~]$ sudo systemctl status flanneld docker kubelet kube-proxy
● flanneld.service - Flanneld overlay address etcd agent
   Loaded: loaded (/usr/lib/systemd/system/flanneld.service; enabled; vendor preset: disabled)
   Active: activating (start) since Tue 2016-05-17 20:21:39 UTC; 14s ago
 Main PID: 2180 (flanneld)
   CGroup: /system.slice/flanneld.service
           └─2180 /usr/bin/flanneld -etcd-endpoints=http://192.168.150.130:2379 -etcd-prefix=/atomic01/network

May 17 20:21:39 localhost.localdomain systemd[1]: flanneld.service holdoff time over, scheduling restart.
May 17 20:21:39 localhost.localdomain systemd[1]: Starting Flanneld overlay address etcd agent...
May 17 20:21:39 localhost.localdomain flanneld[2180]: I0517 20:21:39.744505 02180 main.go:275] Installing signal handlers
May 17 20:21:39 localhost.localdomain flanneld[2180]: I0517 20:21:39.746238 02180 main.go:130] Determining IP address of default interface
May 17 20:21:39 localhost.localdomain flanneld[2180]: I0517 20:21:39.746419 02180 main.go:188] Using 10.0.2.15 as external interface
May 17 20:21:39 localhost.localdomain flanneld[2180]: I0517 20:21:39.746431 02180 main.go:189] Using 10.0.2.15 as external endpoint

● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─10-flanneld-network.conf
        /usr/lib/systemd/system/docker.service.d
           └─flannel.conf
   Active: inactive (dead)
     Docs: http://docs.docker.com

May 17 20:18:38 localhost.localdomain systemd[1]: Dependency failed for Docker Application Container Engine.
May 17 20:18:38 localhost.localdomain systemd[1]: Job docker.service/start failed with result 'dependency'.
May 17 20:20:08 localhost.localdomain systemd[1]: Dependency failed for Docker Application Container Engine.
May 17 20:20:08 localhost.localdomain systemd[1]: Job docker.service/start failed with result 'dependency'.
May 17 20:21:39 localhost.localdomain systemd[1]: Dependency failed for Docker Application Container Engine.
May 17 20:21:39 localhost.localdomain systemd[1]: Job docker.service/start failed with result 'dependency'.

● kubelet.service - Kubernetes Kubelet Server
   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: https://github.com/GoogleCloudPlatform/kubernetes

May 17 20:18:38 localhost.localdomain systemd[1]: Dependency failed for Kubernetes Kubelet Server.
May 17 20:18:38 localhost.localdomain systemd[1]: Job kubelet.service/start failed with result 'dependency'.
May 17 20:20:08 localhost.localdomain systemd[1]: Dependency failed for Kubernetes Kubelet Server.
May 17 20:20:08 localhost.localdomain systemd[1]: Job kubelet.service/start failed with result 'dependency'.
May 17 20:21:39 localhost.localdomain systemd[1]: Dependency failed for Kubernetes Kubelet Server.
May 17 20:21:39 localhost.localdomain systemd[1]: Job kubelet.service/start failed with result 'dependency'.

● kube-proxy.service - Kubernetes Kube-Proxy Server
   Loaded: loaded (/usr/lib/systemd/system/kube-proxy.service; enabled; vendor preset ...
(more)
edit flag offensive delete link more

Comments

To get specific logs for a systemd unit (the same name that follows systemdctl start), you can run `journalctl -u unitname'. For flannel, you can use 'journalctl -u flanneld', etc. It looks like flannel is actually starting. Can you manually start docker? Maybe docker isn't waiting long enough?

nzwulfin ( 2016-05-25 14:59:52 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
1 follower

Stats

Asked: 2016-05-11 21:43:22 +0000

Seen: 2,942 times

Last updated: May 17 '16