Pods stuck in CrashBackLoopOff state

0 votes
One of my Cluster pods is stuck in CrashBackLoopOff state. How do I get out of this state?
Jan 4 in Kubernetes by Ali
• 10,290 points
29 views

1 answer to this question.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
0 votes

There are three possibilities here @Ali,

  • Check your Dockerfile if it a valid ENTRYPOINT
  • Add this line in your dockerfile - easy but dirty solution
CMD exec /bin/bash -c "trap : TERM INT; sleep infinity & wait"
  • set tty as true in your container spec in your deployment file.
spec:
     containers:
     - image: image-name
       name: name
       tty: true     
answered Jan 4 by Lissa

Related Questions In Kubernetes

0 votes
1 answer

Pods stuck in terminating state after deleting ReplicationController

Delete the pods by FORCE, You should.<(-.-)> kubectl ...READ MORE

answered Jan 4 in Kubernetes by ajs3033
• 7,040 points
166 views
+2 votes
2 answers

Kubernetes Pods in Pending State

Hey @Shyam, you get this error because ...READ MORE

answered Oct 31, 2018 in Kubernetes by Kalgi
• 35,800 points
1,353 views
0 votes
1 answer
0 votes
1 answer

Pods IP address from inside a container in the pod

Make sure that your pod yaml file ...READ MORE

answered Aug 29, 2018 in Kubernetes by Kalgi
• 35,800 points
29 views
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
488 views
+3 votes
1 answer
0 votes
1 answer

Error in syncing pod - Kubernetes

You are getting this error because all you're ...READ MORE

answered Jan 4 in Kubernetes by Layla
31 views

© 2018 Brain4ce Education Solutions Pvt. Ltd. All rights Reserved.
"PMP®","PMI®", "PMI-ACP®" and "PMBOK®" are registered marks of the Project Management Institute, Inc. MongoDB®, Mongo and the leaf logo are the registered trademarks of MongoDB, Inc.