Codespace Running in Recovery Mode: "This codespace is currently running in recovery mode due to a container error"

How to fix it

Try these in order — the most common fix is first.

1. 1. Find the error in the creation log

   Copy steps
   1. Open the Command Palette and run "Codespaces: View Creation Log"
   2. Look for the failing step or the JSON/Dockerfile error
   Did this fix it? Yes No

2. 2. Fix the configuration and rebuild

   Copy steps
   1. Edit .devcontainer/devcontainer.json or the Dockerfile to correct the error
   2. Restart the codespace
   3. If restarting does not help, run "Codespaces: Rebuild Container"
   Did this fix it? Yes No

Symptoms

Banner or message: "This codespace is currently running in recovery mode due to a container error." Your extensions, tools and features from devcontainer.json are missing.

Why it happens

• An invalid change to the dev container configuration (devcontainer.json or Dockerfile)
• A failed build step, feature or lifecycle script in the container

This guide also covers

• codespace recovery mode
• codespaces container error recovery mode
• this codespace is currently running in recovery mode

The same problem in other apps

All not loading, error messages & connection guides →

• Ona AWS Runner Failed: ROLLBACK_COMPLETE and ECS Circuit Breaker Errors (Gitpod)
• VS Code Python Interpreter Not Found (VS Code)
• StackBlitz "Cannot load native addon because loading addons is disabled" (StackBlitz)

Other GitHub Codespaces errors

• GitHub Codespaces Creation Failed
• Can't Create a Codespace: No Option to Create on the Repository
• GitHub Codespaces "503 Service Unavailable" Error
• Codespaces "Oh no, it looks like you are offline" and Other Connection Errors
• GitHub Codespaces Port Forwarding Not Working
• Codespace Out of Storage: How to Free Disk Space
• Codespaces Included Usage Used Up: Core Hours and Storage Quota
• Codespaces Prebuild Not Working: "Prebuild Ready" Label Missing