Skip to content

chore: use Debian Trixie devcontainers - #38

Closed
PabloZaiden wants to merge 1 commit into
mainfrom
chore/use-debian-trixie-devcontainers
Closed

chore: use Debian Trixie devcontainers#38
PabloZaiden wants to merge 1 commit into
mainfrom
chore/use-debian-trixie-devcontainers

Conversation

@PabloZaiden

Copy link
Copy Markdown
Owner

Summary

  • move built-in Devbox templates from mcr.microsoft.com/devcontainers/base:noble to mcr.microsoft.com/devcontainers/base:trixie
  • update the built-in fallback descriptions, examples, and repository devcontainer
  • retain the public ubuntu template identifier for compatibility

The official mcr.microsoft.com/devcontainers/base:trixie tag is available.

Move built-in templates, examples, and the development container to the official Debian Trixie base while retaining the ubuntu template identifier for compatibility.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings August 29, 2026 22:21

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

User-facing messaging/docs describe a “Debian Trixie template” fallback even though the actual fallback template identifier remains ubuntu, which is misleading and should be corrected for clarity/compatibility.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR migrates devbox’s built-in devcontainer templates, examples, and repository devcontainer from the Ubuntu noble base image to the Debian Trixie base image while keeping the public ubuntu template identifier for compatibility.

Changes:

  • Switch built-in template base image constants from mcr.microsoft.com/devcontainers/base:noble to ...:trixie and update template descriptions accordingly.
  • Update CLI/help text, README, and tests to reflect the Debian Trixie-based defaults and expected generated configs.
  • Update example workspaces and repo .devcontainer/devcontainer.json to use the Trixie base image.
File summaries
File Description
tests/templates.test.ts Updates expectations for built-in templates to use the Trixie base image and updated descriptions.
tests/examples.test.ts Updates example workspace assertions for generated configs and fallback messaging under the Trixie base.
tests/examples.live.test.ts Updates live test expectations for fallback messaging under the Trixie base.
tests/core.test.ts Updates help text expectations for the new fallback wording and base image.
src/templates.ts Changes built-in template base constants to trixie and updates template descriptions/runtime labels.
src/core.ts Updates CLI help text to describe the new fallback behavior.
src/cli.ts Updates the runtime console message emitted when the fallback template is selected.
README.md Updates documentation to describe Debian Trixie-based defaults and the built-in template list.
examples/smoke-workspace/.devcontainer/devcontainer.json Switches example workspace base image to ...:trixie.
examples/complex-workspace/.devcontainer/devcontainer.json Switches example workspace base image to ...:trixie.
.devcontainer/devcontainer.json Updates repo devcontainer to Debian Trixie naming/linking and base image ...:trixie.
Review details

Suppressed comments (1)

README.md:114

  • This section refers to an "automatic Debian Trixie fallback", but the persisted template identifier is still ubuntu (now backed by Debian Trixie). Using the template name in the docs makes it clearer what will be saved in .devbox/state.json and how to explicitly select the same behavior.
If no repo devcontainer is found and no previous template source is stored, `devbox up` automatically starts from the built-in Debian Trixie template. `devbox rebuild <port>` does the same when there is enough information to create the devbox but no prior workspace state exists. Devbox prints a message when this automatic fallback is used.

`devbox rebuild` reuses the previously selected source for the workspace. If the workspace was started from `--template` or the automatic Debian Trixie fallback, rebuild uses that saved template again. `rebuild --template ...` is intentionally not supported.
  • Files reviewed: 11/11 changed files
  • Comments generated: 3
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread src/cli.ts
Comment on lines 182 to 184
if (resolvedConfig.templateSelection === "fallback") {
console.log("No devcontainer definition found; using built-in ubuntu template.");
console.log("No devcontainer definition found; using built-in Debian Trixie template.");
}
Comment thread src/core.ts
Comment on lines +159 to +160
" up Start or reuse the managed devcontainer; falls back to the built-in Debian Trixie template when none is found.",
" rebuild Recreate the managed devcontainer; falls back to the built-in Debian Trixie template when no repo devcontainer or prior state exists.",
Comment thread README.md
## What it does

- Discovers `.devcontainer/devcontainer.json` or `.devcontainer.json` in the current directory, can target `.devcontainer/<subpath>/devcontainer.json` with a flag, and falls back to the built-in `ubuntu` template when no repo devcontainer is present.
- Discovers `.devcontainer/devcontainer.json` or `.devcontainer.json` in the current directory, can target `.devcontainer/<subpath>/devcontainer.json` with a flag, and falls back to the built-in Debian Trixie template when no repo devcontainer is present.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants