build: retire the docker compose dev environment - #4949
Merged
Conversation
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| .devcontainer/devcontainer.json | Deletes the VS Code configuration whose sole purpose was to launch the removed Compose service. |
| Dockerfile.dev | Removes the obsolete development image definition and its broken legacy runtime dependency. |
| compose.yaml | Removes the legacy code-server development service and its associated mounts and port mapping. |
Reviews (2): Last reviewed commit: "build: retire the docker compose dev env..." | Re-trigger Greptile
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 16, 2026
The brainpower/node-cubicle base image ships a pre-Node-10 runtime (amd64-only, no corepack), so `docker compose build` has been failing with exit 127 for years, and the code-server workflow it powered is long dead. CI and CONTRIBUTING.md do not reference any of this; .devcontainer/devcontainer.json exists only to wire VS Code to the same compose file. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
escapedcat
force-pushed
the
build/retire-dev-container
branch
from
August 16, 2026 09:10
9f6ec14 to
1256a56
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 16, 2026
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.
Description
Deletes the docker-compose-based dev environment:
Dockerfile.dev,compose.yaml, and.devcontainer/(whosedevcontainer.jsonexists only to wire VS Code to that compose file).Motivation and Context
The setup is founder-era and has been broken for a long time:
brainpower/node-cubicleships a pre-Node-10 runtime, is amd64-only, and has no corepack —docker compose buildfails with exit 127 on master today.code-server --no-auth, a remote-dev workflow that predates today's tooling; the devcontainer extension list still recommends prettier, which the repo replaced with oxfmt.Dockerfile.ci(container-build.yml).Stacked on #4948, which touches
Dockerfile.dev— merge that first; this PR then collapses to pure deletions and retargets tomaster.How Has This Been Tested?
Searched the repo for remaining references (
docker compose,compose.yaml,Dockerfile.dev,code-server) — none outside the deleted files.🤖 Generated with Claude Code