Stuart GreigContainer stuck in CrashLoopBackOff?
Running kubectl logs <pod> usually shows nothing because the new container hasn't crashed yet.
The real hero:
kubectl logs <pod> --previous
See exactly why the last one died.
Container stuck in CrashLoopBackOff?
Running kubectl logs <pod> usually shows nothing because the new container hasn't crashed yet.
The real hero:
kubectl logs <pod> --previous
See exactly why the last one died.