Hi all..I have a question (may be basic)..when I create a pod it goes to CrashLo . . .

Kubernetes-Slack Discussions
#1

Sreedevi Velagala:
Hi all…I have a question (may be basic)…when I create a pod it goes to CrashLoopBackOff, we can avoid this by adding a sleep command so that the pod will be in a running state…is it the only option to have a pod in a running state? or am I missing some other options? pls guide me here…thanks

#2

Sreedevi Velagala:
for ex: this type of question:
In the ckad-multi-containers namespace, create a pod named tres-containers-pod, which has 3 containers matching the below requirements:

• The first container named primero runs busybox:1.28 image and has ORDER=FIRST environment variable.
•
• The second container named segundo runs nginx:1.17 image and is exposed at port 8080.
•
• The last container named tercero runs busybox:1.31.1 image and has ORDER=THIRD environment variable.

#3

Paco Bernabé:
Long story short, you need the sleep command when using a busybox image. I’ll come later with a more comprehensive answer.

#4

Sreedevi Velagala:
got it, thanks for the clarification, will wait for your comprehensive answer…thanks for the quick reply

#5

Sreedevi Velagala:
does it apply to nginx image also?

#6

Ruhinda Benjamin:
No. nginx containers keep running without the need of sleep command. busybox is like alpine or ubuntu container when you run the pod without specifying the time it will be active in the background with sleep command it goes into exit / Terminated mode.

#7

Sreedevi Velagala:
noted, thank you