---
name: openshift-ts-app-09-crashloop
title: Why are pods in a `CrashLoopBackOff` status?
description: Learn how to resolve issues when your pods are in a `CrashLoopBackOff` status.
last-updated: 2026-04-09
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why are pods in a `CrashLoopBackOff` status?
{: #ts-app-pod-crashloop}
{: troubleshoot}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}

Learn how to resolve issues when your pods are in a `CrashLoopBackOff` status.
{: shortdesc}

Your pods are in a `CrashLoopBackOff` status.
{: tsSymptoms}


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.
{: tsCauses}


Make sure that you review the [common scenarios where you might need to modify your apps](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploy&format=markdown#openshift_move_apps_scenarios) and follow the documentation in [Moving your apps to Red Hat OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_app&format=markdown#openshift_move_apps).
{: tsResolve}