c70adf6702
* reorganizing security and access sections * updating delete doc * making vscode doc moore os agnostic * updating developing in a codespace * fixing broken links * fixing some broken links * fixing broken topic * fixing broken link * Managing users permissions for your organization and other stuff (#19231) * Add new 'Managing user permissions for your organization' article * Revise 'Managing access and security for Codespaces' and screenshot * Add codespaces to org repo permissions article * Apply suggestions from code review Co-authored-by: Amy Burns <timeyoutakeit@github.com> * fixing title to match slug * fixing broken link * updating personalization doc * updating troubleshooting guide * updating creating doc * adding information about when secrets are used * removing secrets stuff from this PR * Addig order of operations for codespaces * self review fixes * Apply suggestions from code review Co-authored-by: Allison Weins <3174849+2percentsilk@users.noreply.github.com> * renaming quickstart to correct pattern: * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * rewriting re. review comments * Codespaces landingpage (#19053) * adding new tables and linking to info on audit logs * editing some text: * adding new info on how to add image registry login * adding link and fixing table * formatting * formatting * Apply suggestions from code review Co-authored-by: Laura Coursen <lecoursen@github.com> * updaing private image registry secret info and other improvements * some minor fixes * fixing test errors * rewriting registry secret section * rewriting registry secret section * updating link to reflect title * Update content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md Co-authored-by: Laura Coursen <lecoursen@github.com> * updating bullet point * moving codespaces to top-level item * fixing duplicated redirect * Adding some organization for contributors * adding learning codespaces to index file * do not error out if category array is empty * Apply suggestions from code review Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> * fixing broken link * testing what is possible for the landing page * adding first run of landing page * adding new video and intro text * add landing page scaffolding * Update codespaces_code_examples.yml * lint * fixing issues in branch * fixing nav * fixing broken directs * Creating guides sub-landing page * adding topics * removing unused toopic * removing instant * updating landing page and guides page * updating versioning * removing unused topic * removing other versions: * actually fixing broken links * fixing title * fixing intro to suit the landing page * Apply suggestions from code review Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * adding video * adding video * adding correct link for video * removing duplicated guides Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * rewording and reorganizing code samples * fixing some feedback from engineering * Adding doc on Secrets in codespaces (#19248) * adding secrets docs * fixing some broken links * fixing some more broken redirects * copy edit and updating limits for secrets * adding limits for users * Apply suggestions from code review Co-authored-by: Felicity Chapman <felicitymay@github.com> * adding feedback Co-authored-by: Felicity Chapman <felicitymay@github.com> * updating beta banner * adding quickstarts to landing page * removing availability section from reusable Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Allison Weins <3174849+2percentsilk@users.noreply.github.com> Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com>
4.0 KiB
4.0 KiB
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. |
|
|
reference |
|
{% 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/dotfilesto 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.txtto see if there was a problem cloning them.
- Check
/workspaces/.codespaces/.persistedshare/creation.logfor possible issues. Alternatively, you can view thecreation.logby 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-aif you want to remove all images, and--volumesif 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 %}."