Troubleshooting creation and deletion of Codespaces

Creating codespaces

No access to create a codespace

Codespaces are not available for all repositories. If the "Open with Codespaces" button is missing, Codespaces may not be available for that repository. 詳しい情報については、「codespace を作成する」を参照してください。

If you believe your organization has enabled Codespaces, make sure that an organization owner or billing manager has set the spending limit for Codespaces. 詳しい情報については「Codespacesの利用上限の管理」を参照してください。

Codespace does not open when created

If you create a codespace and it does not open:

1. Try reloading the page in case there was a caching or reporting problem.
2. Go to your Codespaces page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page.
3. Retry creating the codespace for the repository to rule out a transient communication failure.

If you still cannot create a codespace for a repository where Codespaces are available, you may need to contact support. For more information, see "Working with support."

Deleting codespaces

The owner of a codespace has full control over it and only they can delete their codespaces. You cannot delete a codespace created by another user.

Container storage

codespace を作成すると、ストレージ容量に限りがあるため、時間の経過とともにスペースを解放する必要がある場合があります。 Try running any of the following commands in the Codespaces terminal to free up storage space.

• Remove packages that are no longer used by using sudo apt autoremove.
• sudo apt clean を使用して apt キャッシュをクリーンアップする.
• See the top 10 largest files in the codespace withsudo find / -printf '%s %p\n'| sort -nr | head -10.
• Delete unneeded files, such as build artifacts and logs.

Some 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).
• 追跡されていないファイルをワーキングツリーから削除する: git clean -i.

Configuration

codespaceの設定の変更でコンテナエラーが生じた場合、codespaceはリカバリモードで動作し、エラーメッセージが表示されます。

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 VS Code Command Palette to retry. For more information, see " Codespaces logs" and "Configuring Codespaces for your project."