CI: de-DINDify
Maintainers usually reply within 1 day
@Rayan-and-beyond is already working on this.
Since Sep 18, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops, infrastructure
Research direction
Start with .github/workflows/vm.yml and the ./integration/container, ./integration/build, and ./integration/system targets named in the issue. Compare the current DIND-based execution with the openSUSE test script for reference. Done means these integration areas run in vm.yml without relying on Docker-in-Docker while covering hosts with their standard configuration.
Written by the indexing model from the issue text.
Description
The current DIND-based CI practically limits the host distribution to Debian userspace + irregular system configuration (systemd, udevd, resolved, etc.) + irregular kernel (Ubuntu, or Oracle on Lima workflows).
https://github.com/moby/moby/blob/8210b0babaed17fbe706a4c5e8c7d0b9c6aba2a1/Dockerfile#L4
https://github.com/moby/moby/blob/8210b0babaed17fbe706a4c5e8c7d0b9c6aba2a1/.github/workflows/test.yml#L35
https://github.com/moby/moby/blob/8210b0babaed17fbe706a4c5e8c7d0b9c6aba2a1/.github/workflows/vm.yml#L46-L47
To cover "real" host OSes with their standard configuration, we have to consider de-DINDifying the CI.
I suggest beginning with de-DINDIfying ./integration/container ./integration/build ./integration/system executed in vm.yml.
openSUSE's test script might be useful for reference https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/containers/docker_engine.pm
- .vm.yml #53672
- .test.yml
- integration
- integration-cli
- integration-flaky
- docker-py
- Dominant language
- Go
- Stars
- 72.2k
- Forks
- 19.3k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 157
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from moby/moby
-
hack/make: copy_binaries fails when only /usr/local/bin/runc is presentPossibly taken @aryansk claimed this 80 days ago. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
moby/moby#53442 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Bug in checking nDotsSet, should be nDotsSet and > 0, leads to failed container name resolution in DinDPossibly taken @NavneetNayak claimed this 115 days ago. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
moby/moby#53104 · 2 comments ·
Maintainers usually reply within 1 day
-
Endpoint (container) name is not passed to network-driver plugins at CreateEndpoint (unlike IPAM drivers, #50586)Possibly taken @claymore666 claimed this 150 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Clarify target terminal for command examples in `docs/contributing/set-up-dev-env.md`May be free again A pull request for this issue was closed without being merged. Openkind/bug status/0-triage
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Default seccomp policy does not allow calling fanotify_init without CAP_SYS_ADMINPossibly taken @ychampion claimed this 123 days ago. Openarea/security/seccomp help wanted kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
moby/moby#49756 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2385 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 5 days
-
项目日志弹出窗尺寸可拉伸功能Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug good first issue priority: P2 status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RhinoLink-Tech/data-fabric#502 ·
Maintainers usually reply within 1 day
-
sweep
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
bketelsen/truenas-mcp#65 ·
Maintainers usually reply within 1 day