install.sh: auto-install devcontainer CLI via standalone bundle#26
Merged
Conversation
When the devcontainer CLI is missing, the installer now bootstraps it via the official @devcontainers/cli standalone installer, which bundles its own Node.js runtime — so no system Node is required. - Installs into ~/.local/share/devcontainer-mcp/devcontainers/ (a folder we own, kept separate from the user's other tools). - Symlinks the resulting binary into INSTALL_DIR/devcontainer so it sits on the same PATH line the installer already tells users to add. - Pre-creates the parent dir so the upstream installer's parent-writable check passes on fresh systems. - Failure is non-fatal: prints a pointer to the upstream install script and continues. devpod and gh remain detect-only (out of scope). install.ps1 delegates to install.sh inside WSL, so Windows users get the auto-install for free.
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
1 participant
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.
When the devcontainer CLI is missing, the installer now bootstraps it via the official @devcontainers/cli standalone installer, which bundles its own Node.js runtime — so no system Node is required.
Behavior
~/.local/share/devcontainer-mcp/devcontainers/(a folder we own, kept separate from the user's other tools).$INSTALL_DIR/devcontainerso it sits on the same PATH line the installer already tells users to add.devpodandghremain detect-only (out of scope).install.ps1delegates toinstall.shinside WSL, so Windows users get the auto-install for free.Verification
Tested locally with a clean
HOME+INSTALL_DIR:Closes the gap where the prior installer just printed
✗ devcontainer — https://…and left the user to figure it out, even though the only blocker was a one-shot download.