<p>I got some error when scheduling pod though ReplicationController:</p>

<pre><code>failedSync   {kubelet 10.9.8.21}   Error syncing pod, skipping: API error (500): Cannot start container 20c2fe3a3e5b5204db4475d1ce6ea37b3aea6da0762a214b9fdb3d624fd5c32c: [8] System error: Activation of org.freedesktop.systemd1 timed out
</code></pre>

<p>The pod is scheduled but cannot run unless I re-deploy it with another image.</p>

<p>I'm using kubelet 1.0.1, CoreOS v773.1.0</p>

<p>The part that says <code>Error syncing pod, skipping: API error</code>  means that kubelet got an error when trying to start a container for your Pod.</p>

<p>Since you use CoreOS, I think you are using rkt, not docker.</p>

<p>I think that rkt uses systemd to start containers.</p>

<p>And I think systemd crashes when the "unit" name starts with an underscore:
<a href="https://github.com/coreos/go-systemd/pull/49" rel="nofollow">https://github.com/coreos/go-systemd/pull/49</a></p>

<p>So, maybe one of your pods or containers has a name that starts with an underscore.  Change that.</p>
