docs/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md

title, intro, redirect_from, versions, type, topics

title	intro	redirect_from	versions	type	topics
Troubleshooting your codespace	Use this guide to help you troubleshoot common issues with your codespace.	/github/developing-online-with-github-codespaces/troubleshooting-your-codespace /github/developing-online-with-codespaces/troubleshooting-your-codespace /codespaces/working-with-your-codespace/troubleshooting-your-codespace	free-pro-team *	reference	Codespaces

{% data reusables.codespaces.release-stage %}

Known Limitations

{% data reusables.codespaces.beta-functionality-limited %}

{% data reusables.codespaces.unsupported-repos %}

{% data variables.product.prodname_vscode %} troubleshooting

Use Issues in the microsoft/vscode repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience.

Configuration troubleshooting

{% data reusables.codespaces.recovery-mode %}

This codespace is currently running in recovery mode due to a container error.

Review the creation logs, update the configuration as needed, and run Codespaces: Rebuild Container in the command palette to retry. For more information, see "Configuring {% data variables.product.prodname_codespaces %} for your project."

dotfiles troubleshooting

• Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use Codespace secrets instead of private dotfiles.
• Check /workspaces/.codespaces/.persistedshare/dotfiles to see if your dotfiles were cloned.
  • If your dotfiles were cloned, try manually re-running your install script to verify it's executable.
  • If your dotfiles weren't cloned, check /workspaces/.codespaces/.persistedshare/EnvironmentLog.txt to see if there was a problem cloning them.
• Check /workspaces/.codespaces/.persistedshare/creation.log for possible issues. Alternatively, you can view the creation.log by navigating to the command palette and entering Codespaces: View Creation Log.

Browser troubleshooting

If you encounter issues while using a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the microsoft/vscode repository by searching for issues labeled with the name of your browser, such asfirefox or safari.

If you encounter issues while using a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the microsoft/vscode repository.

Container storage troubleshooting

When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try any of the following items to free up storage space.

• Remove packages that are no longer by using sudo apt autoremove
• Clean the apt cache by using sudo apt clean
• Delete unneeded files like build artifacts and logs (these are very project-dependent)
• See the top 10 largest files in the codespace: sudo find / -printf '%s %p\n'| sort -nr | head -10

More destructive options:

• Remove unused Docker images, networks, and containers by using docker system prune (append -a if you want to remove all images, and --volumes if you want to remove all volumes)
• Remove untracked files from working tree: git clean -i

Contact us

If you still need help, you can contact us. For more information, see "About {% data variables.product.prodname_codespaces %}."