<p>So I'm trying to setup a master Kubernetes node on coreos in vagrant.  I'm using the example master cloud-config, found here <a href="https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/coreos/cloud-configs/master.yaml" rel="nofollow">https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/coreos/cloud-configs/master.yaml</a> with the addition of this as the first units:</p>

<pre><code>- name: etcd.service
  command: start
- name: fleet.service
  command: start
- name: docker-tcp.socket
  command: start
  enable: true
  content: |
    [Unit]
    Description=Docker Socket for the API

    [Socket]
    ListenStream=2375
    Service=docker.service
    BindIPv6Only=both

    [Install]
    WantedBy=sockets.target
</code></pre>

<p>Once I vagrant up and vagrant ssh, I run <code>sudo systemctl status kube-apiserver</code> and find that <code>kube-apiserver</code> is down due to the fact it can't find <code>etcd.service</code>; however when I do <code>ps -ef | grep etcd</code> etcd is clearly running.  Is there some specific location for etcd.service in systemd or do I have to add a content field to the unit in the cloud-config or something else?</p>

<p>Turns out the example master config is looking for <code>etcd2.service</code>, while the actual file is <code>etcd.service</code> so I changed it in the example units and everything worked.</p>

<p><strong>EDIT</strong></p>

<p>The reason why this worked and was an issue to begin with was that I was using the coresos vagrant box for parallels which is 300~ builds old from the current stable coreos build so it was missing etcd2 all together.</p>
