Why are pods in a CrashLoopBackOff status?

Virtual Private Cloud Classic infrastructure

Learn how to resolve issues when your pods are in a CrashLoopBackOff status.

Your pods are in a CrashLoopBackOff status.

When you try to deploy an app that works on community Kubernetes platforms, you might see this status or a related error message because Red Hat OpenShift sets up stricter security settings by default than community Kubernetes.

Make sure that you review the common scenarios where you might need to modify your apps and follow the documentation in Moving your apps to Red Hat OpenShift.