Docker-in-Docker feature with `moby: true` not working on `trixie`

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
debian, docker
Domain
devops, infrastructure

Research direction

Start with .devcontainer/dhi-docker/Dockerfile, which the issue identifies as the bookworm workaround, and compare its base image with the failing trixie setup. Reproduce the Docker-in-Docker feature with moby: true, then review the linked upstream issues to determine whether this repository should change its base image or only document the moby: false workaround.

Written by the indexing model from the issue text.

Description

Docker feature (dind) with moby: true is not supported with trixie:

The 'moby' option is not supported on Debian 'trixie' because 'moby-cli' and related system packages have been removed from that distribution.
0.116 (!) To continue, either set the feature option '"moby": false' or use a different base image (for example: 'debian:bookworm' or 'ubuntu-24.04').
0.116 ERROR: Feature "Docker (Docker-in-Docker)" (ghcr.io/devcontainers/features/docker-in-docker) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/docker-in-docker for help troubleshooting this error.

Workaround: use bookworm instead, see here: https://github.com/mathieu-benoit/devcontainers/blob/main/.devcontainer/dhi-docker/Dockerfile#L1.

Related to this https://github.com/devcontainers/features/issues/1494 and this https://github.com/devcontainers/features/issues/1466:

Requesting users to use moby: false when the base image is built on debian trixie.

Dominant language
Shell
Stars
1
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mathieu-benoit/devcontainers

All issues in mathieu-benoit/devcontainers

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.