danieski caballero:
Hello, Crashlookback error at the time of creating a pod with busybox on the Mock exam 2. I can make other pods with nginx but not with that image.
Nitish Patni:
do check describe pod which is crashing and u will get some idea why crashloop is happening.
Nitish Patni:
check container top side see if command has some mistake
Alistair Mackay:
Is there a command the busybox pod should be running?
The busybox image has nothing to do when it starts so it will simply exit, and that will be counted as a crashloop.
nginx pods however starts a web server process in the foreground, meaning it is doing something and does not exit. I don’t have the question in front of me, but busybox starting on its own would require something like
kubectl run busybox --image busybox --command -- sleep 3600
to not exit immediately
Santosh Kaluskar:
Possible… as the Reason for termination is Completed
> While the BusyBox Docker Official Image is a great base for other projects, BusyBox works well with the Kubernetes initContainer feature.
https://www.docker.com/blog/use-cases-and-tips-for-using-the-busybox-docker-official-image/|https://www.docker.com/blog/use-cases-and-tips-for-using-the-busybox-docker-official-image/
Alistair Mackay:
I was, and am using my phone, so could not load the lab to verify what the question was actually asking. Next time I’m at a computer I can follow up properly if this is still outstanding.