Fix codespace boot failure by using updateContentCommand for npm ci#208
Draft
Fix codespace boot failure by using updateContentCommand for npm ci#208
Conversation
…ostCreateCommand Co-authored-by: rajbos <6085745+rajbos@users.noreply.github.com>
Co-authored-by: rajbos <6085745+rajbos@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix codespace boot failure with current configuration
Fix codespace boot failure by using updateContentCommand for npm ci
Feb 11, 2026
Owner
|
Booting the codespace still fails on connecting, needs more info to find the issue. Might just be the image itself? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codespaces fail immediately on boot with no logs. The
postCreateCommandhook times out during container creation when runningnpm ci.Changes
.devcontainer/devcontainer.json: ReplacepostCreateCommandwithupdateContentCommandCONTRIBUTING.md: Document the lifecycle hook choice and rationaleContext
The devcontainer lifecycle runs:
onCreateCommand→updateContentCommand→postCreateCommand→postStartCommand.Dependency installation belongs in
updateContentCommand(runs after content sync) rather thanpostCreateCommand(one-time container creation, blocking, prone to timeout).💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.