Skip to content

Add devcontainer CLI instructions #8635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cknitt merged 2 commits into from
Sep 7, 2026
+17 −0
Merged

Add devcontainer CLI instructions #8635

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6249cf7
Add devcontainer CLI instructions
cknitt Sep 7, 2026
2cf5c94
Ignore local devcontainer lockfile
cknitt Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .devcontainer/.gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
devcontainer-lock.json

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the feature lockfile under version control

When contributors create this container from separate clean checkouts, ignoring the generated lockfile means each checkout independently resolves the floating Feature references (github-cli:1 with latest and node:1). This can install different Feature implementations over time and undermines the documented stable environment; commit devcontainer-lock.json so all contributors use the same resolved versions and integrity hashes.

Useful? React with 👍 / 👎.


15 changes: 15 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,21 @@ Run the `Dev Containers: Rebuild and Reopen in Container` action to get started.

You can also open this dev container with [GitHub Codespaces](https://github.com/features/codespaces/).

Alternatively, install the [Dev Container CLI](https://github.com/devcontainers/cli) through npm:

```sh
npm install -g @devcontainers/cli
```

Then create the development container and open a shell in it:

```sh
devcontainer up --workspace-folder .
devcontainer exec --workspace-folder . zsh
```

Use the Dev Container tooling rather than building `.devcontainer/Dockerfile` directly. The tooling installs the features declared in `devcontainer.json`, including Node.js, and runs the post-create command. A plain `docker build` does not apply these features or lifecycle commands.

## Building the Compiler

Main targets:
Expand Down
Loading