<p dir="auto">I have an auto-scaling group that's a duplicate of the one created by <code class="notranslate">kube-up</code> for AWS using Ubuntu 15.04 minions, the only difference being it requests spot instances. When a spot instances is rebooted for whatever reason (they aren't stable), it fails to launch any pods because of an aufs error.  I don't know if this only happens with spot instances, but this was the case for me this time, so it might be relevant.</p>
<p dir="auto">This is not the first time I've seen this error.  If I manually terminate the instance, which causes the ASG to request a new spot instance, the new node will launch pods successfully.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Error pulling image (prd-beb0010d) from me/project, Driver aufs failed to create image rootfs 08ecf065655b44634e66f45201a7d379d30ba877791b1765322dabf57e993f11: open /mnt/ephemeral/docker/aufs/layers/4a5e6db8c0693a16de88b7559ded7c1cb804018571b137e13abb1713ce6a71cf: no such file or directory
API error (500): error creating aufs mount to /mnt/ephemeral/docker/aufs/mnt/38143c22f7a2644da4bc0cd8782a24a95274eaf255c9468dedbeea2d7c4b2b76-init: invalid argument"><pre class="notranslate"><code class="notranslate">Error pulling image (prd-beb0010d) from me/project, Driver aufs failed to create image rootfs 08ecf065655b44634e66f45201a7d379d30ba877791b1765322dabf57e993f11: open /mnt/ephemeral/docker/aufs/layers/4a5e6db8c0693a16de88b7559ded7c1cb804018571b137e13abb1713ce6a71cf: no such file or directory
API error (500): error creating aufs mount to /mnt/ephemeral/docker/aufs/mnt/38143c22f7a2644da4bc0cd8782a24a95274eaf255c9468dedbeea2d7c4b2b76-init: invalid argument
</code></pre></div>
<p dir="auto">Running Kubernetes 1.4.1 at AWS (Ubuntu 14.04 LTS). Kubernetes cluster is spinned with 'contrib/ansible' playbook with the only change of <code class="notranslate">--cloud-provider aws</code> argument added to all cluster internal services (such as kubelet).</p>
<p dir="auto">After spinning up and terminating several pods with config like below</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="apiVersion: extensions/v1beta1 
kind: Deployment 
metadata:
  name: kafka1
spec:
  replicas: 1
  template:
    spec:
      containers:
      - name: kafka1
        image: daniilyar/kafka
        ports:
        - containerPort: 9092 
          name: clientconnct
          protocol: TCP
        volumeMounts:
        - mountPath: /kafka
          name: storage
      volumes:
      - name: storage
        awsElasticBlockStore:
          volumeID: vol-56676d83
          fsType: ext4"><pre class="notranslate"><code class="notranslate">apiVersion: extensions/v1beta1 
kind: Deployment 
metadata:
  name: kafka1
spec:
  replicas: 1
  template:
    spec:
      containers:
      - name: kafka1
        image: daniilyar/kafka
        ports:
        - containerPort: 9092 
          name: clientconnct
          protocol: TCP
        volumeMounts:
        - mountPath: /kafka
          name: storage
      volumes:
      - name: storage
        awsElasticBlockStore:
          volumeID: vol-56676d83
          fsType: ext4
</code></pre></div>
<p dir="auto">I see a following error in kubelet logs logged each 40-60 sec:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="E1018 21:03:09.616581   22780 fs.go:332] Stat fs failed. Error: no such file or directory"><pre class="notranslate"><code class="notranslate">E1018 21:03:09.616581   22780 fs.go:332] Stat fs failed. Error: no such file or directory
</code></pre></div>
<p dir="auto">Error contains a different line number than in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="118601311" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/17725" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/17725/hovercard" href="https://github.com/kubernetes/kubernetes/issues/17725">#17725</a> , so I assume this one is probably not a duplicate.</p>