devcontainer: pin prebuild base to bookworm#89
Conversation
The rolling base:debian tag now resolves to trixie (Debian 13), and the docker-in-docker feature's Moby apt packages have no trixie repo yet, so the prebuild failed with "Unsupported distribution version 'trixie'". Pin to bookworm (Debian 12) until docker-in-docker supports trixie. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 2 hours, 16 minutes, and 57 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Pins the devcontainer prebuild base image to a supported Debian release to restore the DevContainer Prebuild workflow after the upstream rolling :debian tag began resolving to Debian trixie (13), which the docker-in-docker feature does not currently support.
Changes:
- Change the prebuild base image from
mcr.microsoft.com/devcontainers/base:debian(rolling) tomcr.microsoft.com/devcontainers/base:bookworm(Debian 12). - Add inline rationale documenting the failure mode (
Unsupported distribution version 'trixie') and why bookworm is chosen.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The ":1" pin resolves to a stale frozen 1.x image (the feature has no 1.x releases anymore — it's at 3.x). That old script runs a global `pip install docker-compose` on bookworm/arm64, which fails under PEP 668 (externally-managed-environment) — the arm64 prebuild failure that survived the bookworm pin (#89), the v2-plugin switch (#90), and the dockerDashComposeVersion=none change (#91), because none of them affect which feature version runs. 2.x gates the entire compose/pip block behind `!= none`, so with dockerDashComposeVersion=none there is no pip on arm64 at all. amd64 was unaffected (it gets a prebuilt v1 binary). `docker compose` v2 still comes from the moby-compose package. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Fix
The
DevContainer Prebuildworkflow failed onmainafter #88 merged. Root cause:The rolling
mcr.microsoft.com/devcontainers/base:debiantag now resolves to trixie (Debian 13), and thedocker-in-dockerfeature's Moby apt packages don't have a trixie repo yet. This pins the prebuild base image to bookworm (Debian 12), which docker-in-docker supports.(The
--cache-from ... not foundlines in the failed log were just first-run noise — the buildcache tags don't exist until the first successful run — not the cause.)Verification
The prebuild image only builds in CI, so this will be confirmed green by the
DevContainer Prebuildrun on merge tomain.🤖 Generated with Claude Code