My Oracle Support Banner

Kubernetes Pods Stops With "CrashLoopBackOff" Status (Doc ID 2442917.1)

Last updated on SEPTEMBER 07, 2018

Applies to:

Linux OS - Version 1.0.0-1 and later
Oracle Cloud Infrastructure - Version N/A to N/A [Release 1.0]
Linux x86-64
Linux x86-64

Symptoms

When trying to deploy a kubernetes pod it fails with

ERROR
-----------------------

NAME READY STATUS RESTARTS AGE
linuxos-78d5fc9cb9-wnxjq 0/1 CrashLoopBackOff 1 13s            <<<<<<<<<<<<<-----
testnginx-5d65976cf5-xll6r 1/1 Running 0 2d

$ kubectl describe pod
Name: linuxos-5979fb4867-d8kjn
Namespace: default
Node: worker2.vagrant.vm/<ip>
Start Time: Fri, 08 Jun 2018 09:11:15 +0000
Labels: pod-template-hash=1535960423
run=linuxos
Annotations: <none>
Status: Running
IP: <ip>
Controlled By: ReplicaSet/linuxos-5979fb4867
Containers:
linuxos:
Container ID: docker://0bfa078297d47928f31eff5b2f64bdbd9638bd574a53b97116a9274a00fc4641
Image: oraclelinux:7.5
Image ID:
docker-pullable://oraclelinux@sha256:2a56a8a3645e985b735421b65d4a9273072447a2046a5ba89a8a97d172a7a2cc
Port: <none>
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Completed
Exit Code: 0                                        <<<<<<<<<<<<<<<<<<<<<<<<<< note the 0 (zero) status exit code
Started: Fri, 08 Jun 2018 09:15:00 +0000
Finished: Fri, 08 Jun 2018 09:15:00 +0000
Ready: False
Restart Count: 5
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-86vgb
(ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
default-token-86vgb:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-86vgb
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From
Message
---- ------ ---- ----
-------
Normal SuccessfulMountVolume 5m kubelet,worker2.vagrant.vm MountVolume.SetUp succeeded for volume"default-token-86vgb"
Normal Pulling 5m kubelet,worker2.vagrant.vm pulling image "oraclelinux:7.5"
Normal Scheduled 5m default-scheduler Successfully assigned linuxos-5979fb4867-d8kjn to worker2.vagrant.vm
Normal Pulled 4m kubelet,worker2.vagrant.vm Successfully pulled image "oraclelinux:7.5"
Normal Pulled 3m (x4 over 4m) kubelet,worker2.vagrant.vm Container image "oraclelinux:7.5" already present on machine
Normal Created 3m (x5 over 4m) kubelet,worker2.vagrant.vm Created container
Normal Started 3m (x5 over 4m) kubelet,worker2.vagrant.vm Started container
Warning BackOff 17s (x23 over 4m) kubelet,worker2.vagrant.vm Back-off restarting failed container

 

There is also no output when trying to view the log results

 

$ kubectl -n default logs -p linuxos-5979fb4867-pt7hv
$ kubectl logs -p linuxos-5979fb4867-pt7hv
$ kubectl logs linuxos-5979fb4867-pt7hv

Similarly no log is present in /var/log/containers

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.