jpetazzo/dind resource
Docker in Docker observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4762
- days_rel: n/a
- days_push: 2968
- n_releases_24m: 0
Adoption not part of the score
2528 stars · 554 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Docker image recipe that lets you run a Docker daemon inside a Docker container using the --privileged flag. It is now obsolete, superseded by the official docker:dind image.
Use cases
- run docker inside a docker container
- spin up containers from a jenkins ci container
- nested docker daemon for testing
- expose an inner docker daemon over a tcp port
When to choose
- you need to understand how docker-in-docker works under the hood
- you are stuck on a very old docker version without the official dind image
When to avoid
- you want to run docker-in-docker today - use the official docker:dind image instead
- you want ci containers to build images - use socket mounting or rootless alternatives
- you need a maintained solution
Facets
infra-config · maturity abandoned
container-runtime developer-tools deployment developer-tools cli docker-in-docker ci-cd obsolete shell-script privileged-containers containers devops docker linux
1 source
- readme: https://github.com/jpetazzo/dind · fetched 2026-08-28 · efa68712b825
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| jpetazzo/dind | main | 10 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem