<p>I'm trying to set up a kubernetes cluster on 2 nodes , centos 7.1 using this <a href="http://severalnines.com/blog/installing-kubernetes-cluster-minions-centos7-manage-pods-services" rel="nofollow noreferrer">guide</a>. However when I attempt to start the services on the minion like so:</p>

<pre><code>for SERVICES in kube-proxy kubelet docker flanneld; do
    systemctl restart $SERVICES
    systemctl enable $SERVICES
    systemctl status $SERVICES 
done
</code></pre>

<p>I get the following error:</p>

<pre><code>-- Logs begin at Wed 2015-12-23 13:00:41 UTC, end at Wed 2015-12-23 16:03:54 UTC. --
Dec 23 16:03:47 sc-test2 systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE
Dec 23 16:03:47 sc-test2 systemd[1]: Failed to start Docker Storage Setup.
-- Subject: Unit docker-storage-setup.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker-storage-setup.service has failed.
-- 
-- The result is failed.
Dec 23 16:03:47 sc-test2 systemd[1]: Unit docker-storage-setup.service entered failed state.
Dec 23 16:03:48 sc-test2 flanneld[36477]: E1223 16:03:48.187350 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
Dec 23 16:03:49 sc-test2 flanneld[36477]: E1223 16:03:49.189860 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
Dec 23 16:03:50 sc-test2 flanneld[36477]: E1223 16:03:50.192894 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
Dec 23 16:03:51 sc-test2 flanneld[36477]: E1223 16:03:51.194940 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
Dec 23 16:03:52 sc-test2 flanneld[36477]: E1223 16:03:52.197222 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
Dec 23 16:03:53 sc-test2 flanneld[36477]: E1223 16:03:53.199248 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
Dec 23 16:03:54 sc-test2 flanneld[36477]: E1223 16:03:54.201160 36477 network.go:53] Failed to retrieve network config: 100: Key not found (/atomic.io)
</code></pre>

<p>I'm sure I set the key on the master with :
etcdctl mk /coreos.com/network/config '{"Network":"172.17.0.0/16"}'</p>

<p>By far installation seems to be the hardest bit on using kubernetes :(</p>

Jonathan
<p>Today's christmas but I spent the whole day trying to get this to work :) This is what I did:</p>

<h2>#1 FLANNEL</h2>

<p>As mentioned I'd set the flannel etcd key on the master with:</p>

<p><code>etcdctl mk /coreos.com/network/config '{"Network":"172.17.0.0/16"}'</code></p>

<p>but I got this error when trying to start flannel on the minion:</p>

<p><code>Failed to retrieve network config: 100: Key not found (/atomic.io)</code></p>

<p>So I edited the <code>/etc/sysconfig/flanneld</code> file on the minion from:</p>

<pre><code># Flanneld configuration options  

# etcd url location.  Point this to the server where etcd runs
FLANNEL_ETCD="http://master:2379"

# etcd config key.  This is the configuration key that flannel queries
# For address range assignment
FLANNEL_ETCD_KEY="/coreos.com/network"

# Any additional options that you want to pass
#FLANNEL_OPTIONS=""

to:

# Flanneld configuration options  

# etcd url location.  Point this to the server where etcd runs
FLANNEL_ETCD="http://master:2379"

# etcd config key.  This is the configuration key that flannel queries
# For address range assignment
FLANNEL_ETCD_KEY="/atomic.io/network"

# Any additional options that you want to pass
#FLANNEL_OPTIONS=""
</code></pre>

<p>i.e. changed the FLANNEL_ETCD key.</p>

<p>After this <code>systemctl start flanneld</code> worked.</p>

<h2>#2 DOCKER</h2>

<p>I didn't find a way to make the version installed as a dependency by kubernetes work so I uninstalled it and following the docker docs for Centos installed docker-engine and manually created a docker.service file for systemctl.</p>

<p><code>cd /usr/lib/systemd/system</code></p>

<p>and the contents of the docker.service:</p>

<pre><code>[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target docker.socket
Requires=docker.socket
Requires=flanneld.service
After=flanneld.service

[Service]
EnvironmentFile=/etc/sysconfig/flanneld
ExecStart=/usr/bin/docker daemon -H fd:// --bip=${FLANNEL_SUBNET}
Restart=on-failure
RestartSec=5


[Install]
WantedBy=multi-user.target
</code></pre>

<p>then start and enable the daemon with systemctl as well as query the status.</p>

<pre><code>systemctl restart docker
systemctl enable docker
systemctl status docker
</code></pre>
