Hello Team, did anyone experienced the below error while creating busybox pods i . . .

Kubernetes-Slack Discussions
#1

suneel:
Hello Team, did anyone experienced the below error while creating busybox pods in mock exam ?

Normal   Pulled     26s (x5 over 2m2s)  kubelet            Container image "busybox:1.28" already present on machine
#2

Tej_Singh_Rana:
Hello, @suneel
It’s not an error. It’s just a message that busybox:1.28 already available in the server.

#3

Tej_Singh_Rana:
You can check via docker images command.

#4

suneel:
Understand, but the pod was in crashing or in pending state, how can we fix it if the same issue occurs again

#5

Tej_Singh_Rana:
Container is not meant to host an image only, its for active running processes. In the busybox image, there is no active process defined on it so that’s why it’s getting crash.

#6

Tej_Singh_Rana:
Try to add sleep 4800 in command field.

spec:
- name: xyz
  image: busybox:1.28
  command: 
   - sleep 
   - 4800
...
1 Like