ExecStartPre=/usr/bin/rkt rm --uuid-file=/var/run/kubelet-pod.uuid (code=exited, status=254)

[brant4test]

Hi, Team,
Any one met this error before? Thanks!
$ sudo systemctl status kubelet
● kubelet.service
   Loaded: loaded (/etc/systemd/system/kubelet.

service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Thu 2017-05-18 17:30:17 UTC; 8s ago
  Process: 14338 ExecStart=/usr/lib/coreos/kubelet-wrapper --api-servers=http://127.0.0.1:8080 --register-schedulable=false --cni-conf-dir=/etc/kubernetes/cni/net.d --netw
  Process: 14335 ExecStartPre=/usr/bin/mkdir -p /opt/cni/bin (code=exited, status=0/SUCCESS)
  Process: 14324 ExecStartPre=/usr/bin/rkt rm --uuid-file=/var/run/kubelet-pod.uuid (code=exited, status=254)
  Process: 14314 ExecStartPre=/usr/bin/mkdir -p /var/log/containers (code=exited, status=0/SUCCESS)
 Main PID: 14338 (code=exited, status=254)
      CPU: 331ms

May 18 17:30:17 ip-10-3-0-11 systemd[1]: kubelet.service: Main process exited, code=exited, status=254/n/a
May 18 17:30:17 ip-10-3-0-11 systemd[1]: kubelet.service: Unit entered failed state.
May 18 17:30:17 ip-10-3-0-11 systemd[1]: kubelet.service: Failed with result 'exit-code'.
lines 1-13/13 (END)


This is my configuration
vi /etc/systemd/system/kubelet.service

[Service]
Environment=KUBELET_IMAGE_TAG=quay.io/coreos/hyperkube:v1.6.3_coreos.0
Environment="RKT_RUN_ARGS=--uuid-file-save=/var/run/kubelet-pod.uuid \
  --volume var-log,kind=host,source=/var/log \
  --mount volume=var-log,target=/var/log \
  --volume dns,kind=host,source=/etc/resolv.conf \
  --mount volume=dns,target=/etc/resolv.conf" \
ExecStartPre=/usr/bin/mkdir -p /etc/kubernetes/manifests
ExecStartPre=/usr/bin/mkdir -p /var/log/containers
ExecStartPre=-/usr/bin/rkt rm --uuid-file=/var/run/kubelet-pod.uuid
ExecStartPre=/usr/bin/mkdir -p /opt/cni/bin
ExecStart=/usr/lib/coreos/kubelet-wrapper \
  --api-servers=http://127.0.0.1:8080 \
  --register-schedulable=false \
  --cni-conf-dir=/etc/kubernetes/cni/net.d \
  --network-plugin=cni \
  --container-runtime=docker \
  --allow-privileged=true \
  --pod-manifest-path=/etc/kubernetes/manifests \
  --hostname-override=10.3.0.11 \
  --cluster_dns=10.3.0.10 \
  --cluster_domain=cluster.local
ExecStop=-/usr/bin/rkt stop --uuid-file=/var/run/kubelet-pod.uuid
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

[Luca BRUNO]

On Thursday, May 18, 2017 10:53:03 AM UTC brant4test wrote:
> Hi, Team,
> Any one met this error before? Thanks!

> Main PID: 14338 (code=exited, status=254)

This one means that rkt itself failed before starting the pod.
However, it should have left some error logs in journal, I'm not sure why you
don't see anything.

Can you check the whole journal to see if it contains some more detail?
If not, can you add a `--debug` to rkt options and/or try to run the same
thing manually?

Also, which ContainerLinux release is this?

Ciao, Luca

--
"If you build a wall, think of what you leave outside it" - Italo Calvino

[Turgos]

did you get solution for this problem? I have exact same issue.

Thank you