Skip to content
Go back

Week 13: Docker-in-Docker Workflows

Edit page

🐳 Docker 360 β€” Week 13 of 16 | Building Docker images from inside containers

🎯 Learning Objective

Kabhi socha hai ke CI pipeline ke andar β€” jo khud ek container me chal rahi hai β€” Docker image kaise build hoti hai? Is week me tum seekhoge Docker-in-Docker (DinD) kya hai, Docker socket mount karne se is me kya farq hai, dono ke security trade-offs kya hain, aur ek real CI-style workflow khud bana kar test karoge. Week ke end tak tum confidently decide kar sako ge ke kab DinD use karna hai aur kab socket mount.

🎨 Visual Diagrams

Socket mount vs DinD β€” architecture ka farq:

OPTION A: Docker socket mount (container shares HOST daemon)
=============================================================

  Host Machine
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  dockerd (HOST daemon)                           β”‚
  β”‚   β”œβ”€β”€ image cache (shared!)                      β”‚
  β”‚   β”œβ”€β”€ containers A, B, C ...                     β”‚
  β”‚                                                  β”‚
  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”‚
  β”‚  β”‚  "builder" container                    β”‚     β”‚
  β”‚  β”‚   docker CLI ──► /var/run/docker.sock ──┼──┐  β”‚
  β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚  β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”‚β”€β”€β”˜
                                                  β”‚
              talks to the HOST daemon β—„β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

  Result: "docker build" inside container fills the HOST's
  image cache. "docker ps" shows HOST containers.


OPTION B: Docker-in-Docker (fully separate daemon)
==================================================

  Host Machine
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  dockerd (HOST daemon)                           β”‚
  β”‚   β”œβ”€β”€ image cache (untouched βœ“)                  β”‚
  β”‚   β”‚                                              β”‚
  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”‚
  β”‚  β”‚  dind container (--privileged)          β”‚     β”‚
  β”‚  β”‚   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”      β”‚     β”‚
  β”‚  β”‚   β”‚  dockerd (INNER daemon)      β”‚      β”‚     β”‚
  β”‚  β”‚   β”‚   β”œβ”€β”€ own image cache       β”‚      β”‚     β”‚
  β”‚  β”‚   β”‚   └── build containers      β”‚      β”‚     β”‚
  β”‚  β”‚   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜      β”‚     β”‚
  β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β”‚
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

  Result: builds happen in an isolated daemon. Host stays clean.

CI pipeline me DinD ka flow:

  Git push
     β”‚
     β–Ό
  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  CI runner (host)   β”‚
  β”‚                     β”‚
  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚       β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
  β”‚  β”‚ job container │──┼──────►│  dind service    β”‚
  β”‚  β”‚ docker CLI    β”‚  β”‚  TLS  β”‚  inner dockerd   β”‚
  β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  │◄───────  builds image    β”‚
  β”‚                     β”‚       β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  β”‚   docker build -t           β”‚
  β”‚   myapp:$SHA .              β–Ό
  β”‚                     β”‚  registry push
  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

🧠 Theory Deep Dive

Docker socket mount kya hai?

Har Linux host par Docker daemon ek Unix socket par sunta hai: /var/run/docker.sock. Agar tum is file ko container ke andar mount kar do:

docker run -v /var/run/docker.sock:/var/run/docker.sock docker:24-cli docker ps

…to container ke andar wali Docker CLI host ke daemon se baat karti hai. Iska matlab ye hai ke container host par kuch bhi kar sakta hai β€” naye containers start karna, images delete karna, volumes parhna. Ye powerful hai, lekin security ke lihaz se khatarnak bhi: socket ka access effectively host par root access ke barabar hai.

Docker-in-Docker kya hai?

DinD me container ke andar ek alag Docker daemon chalta hai (docker:dind image). Iske liye container ko --privileged flag chahiye hota hai, kyunke inner daemon ko kernel features (cgroups, namespaces, storage drivers) ki zaroorat hoti hai. Bahar wali CLI inner daemon se TLS-encrypted TCP par baat karti hai β€” modern docker:dind images ye certificates khud generate kar leti hain.

Side-by-side comparison

PointSocket mountDocker-in-Docker
DaemonHost ka daemon share hota haiAlag, isolated daemon
SetupBohat simple β€” ek -v flag--privileged + TLS config chahiye
Image cacheHost ka cache use hota hai (ganda ho sakta hai)Apna cache, host saaf rehta hai
SecuritySocket = host root ke barabarPrivileged container bhi risky hai
Parallel buildsEk dusre se takra sakte hainHar job ka apna daemon β€” clean isolation
Best forLocal dev tools (e.g. Portainer, watchtower)CI pipelines (GitLab CI, Jenkins agents)

--privileged ke caveats

--privileged lagbhag saari container isolation khatam kar deta hai β€” container host ke devices access kar sakta hai. Iska matlab ye hai ke agar dind container compromise ho jaye, attacker ke paas host tak pohanchne ka rasta hai. Isi liye DinD ko sirf trusted CI workloads me use karo, aur in alternatives ko zehen me rakho:

AlternativeKab use karo
Socket mount + strict access controlLocal tooling, single-tenant dev machine
Rootless DinD (docker:24-dind-rootless)Jab privileged allow na ho
Remote Docker daemon / Docker contextBuilds dedicated builder host par
Kaniko / BuildKit (rootless builds)Kubernetes-based CI (unprivileged)

πŸ’» Hands-On Lab

Lab 1 β€” Socket mount: host daemon ko container se control karna

Step 1: Socket mount karke host ke containers dekho:

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock docker:24-cli docker ps --format '{{.Names}}'

βœ… Expected result: Tumhare host par chalne wale containers ke naam print honge β€” ye proof hai ke container host ke daemon se baat kar raha hai.

Step 2: Ek test image build karke dekho ke wo host ke cache me jati hai:

mkdir -p /tmp/sock-demo && cd /tmp/sock-demo
printf 'FROM alpine\nCMD ["echo","socket build"]\n' > Dockerfile
docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/sock-demo:/work -w /work docker:24-cli docker build -t sock-demo .
docker images sock-demo

βœ… Expected result: docker images sock-demo host par image dikhayega β€” matlab build host ke daemon ne ki, container sirf remote control tha.

Step 3: Safai:

docker rmi sock-demo

Lab 2 β€” DinD: apna isolated daemon chalana

Step 1: Network aur volumes banao:

docker network create dind-net
docker volume create dind-data
docker volume create dind-certs

Step 2: DinD daemon start karo (TLS certs khud banenge):

docker run -d --privileged --name dind \
  --network dind-net \
  -e DOCKER_TLS_CERTDIR=/certs \
  -v dind-data:/var/lib/docker \
  -v dind-certs:/certs \
  docker:24-dind

Step 3: Client container se inner daemon se connect karo:

docker run --rm --network dind-net \
  -e DOCKER_HOST=tcp://dind:2376 \
  -e DOCKER_TLS_VERIFY=1 \
  -e DOCKER_CERT_PATH=/certs/client \
  -v dind-certs:/certs:ro \
  docker:24-cli sh -c "sleep 3; docker info --format 'Inner daemon version: {{.ServerVersion}}'"

βœ… Expected result: Inner daemon version: 24.x.x β€” ek completely alag daemon jawab de raha hai, host wala nahi.

Step 4: Inner daemon ke andar image build karo:

mkdir -p /tmp/dind-demo && cd /tmp/dind-demo
printf 'FROM alpine\nCMD ["echo","built inside DinD"]\n' > Dockerfile
docker run --rm --network dind-net \
  -e DOCKER_HOST=tcp://dind:2376 \
  -e DOCKER_TLS_VERIFY=1 \
  -e DOCKER_CERT_PATH=/certs/client \
  -v dind-certs:/certs:ro \
  -v /tmp/dind-demo:/work -w /work \
  docker:24-cli sh -c "docker build -t dind-test . && docker run --rm dind-test"

βœ… Expected result: built inside DinD print hoga β€” aur phir docker images dind-test host par kuch nahi dikhayega, kyunke image inner daemon ke cache me hai. Isolation ka saboot!

Step 5: Lab 1 se compare karo:

docker images dind-test   # kuch nahi milega β€” host cache saaf hai βœ“

Lab 3 β€” CI-style compose setup (GitLab CI jaisa pattern)

Step 1: Ek project folder me ye compose.yaml likho:

services:
  docker:
    image: docker:24-dind
    privileged: true
    environment:
      DOCKER_TLS_CERTDIR: /certs
    volumes:
      - dind-data:/var/lib/docker
      - dind-certs:/certs
  builder:
    image: docker:24-cli
    depends_on:
      - docker
    environment:
      DOCKER_HOST: tcp://docker:2376
      DOCKER_TLS_VERIFY: 1
      DOCKER_CERT_PATH: /certs/client
    volumes:
      - dind-certs:/certs/client:ro
      - ./app:/work
    working_dir: /work
    # daemon ke ready hone ka wait, phir build + test
    command: sh -c "sleep 5 && docker build -t ci-demo . && docker run --rm ci-demo"

volumes:
  dind-data:
  dind-certs:

Step 2: Ek chhoti app aur Dockerfile banao:

mkdir -p /tmp/ci-dind/app && cd /tmp/ci-dind
printf 'FROM alpine\nCMD ["echo","CI build successful"]\n' > app/Dockerfile

(compose.yaml upar wali file isi folder me rakho)

Step 3: Chalao:

docker compose -f compose.yaml up --build

βœ… Expected result: Logs me CI build successful nazar aayega β€” ye exactly wohi pattern hai jo GitLab CI use karta hai:

# GitLab CI me isi concept ka istemal (reference ke liye)
# image: docker:24-cli
# services:
#   - docker:24-dind
# variables:
#   DOCKER_HOST: tcp://docker:2376
#   DOCKER_TLS_CERTDIR: "/certs"
# build-job:
#   script:
#     - docker build -t myapp:$CI_COMMIT_SHORT_SHA .
#     - docker push myapp:$CI_COMMIT_SHORT_SHA

Step 4: Safai:

cd /tmp/ci-dind && docker compose -f compose.yaml down -v
docker stop dind && docker rm dind
docker network rm dind-net
docker volume rm dind-data dind-certs

βœ… Checkpoint

Q1: Socket mount karne par container ke andar docker ps kya dikhata hai? A: Host ke daemon ke containers β€” kyunke CLI host ke daemon se baat kar rahi hoti hai, container ke apne daemon se nahi.

Q2: DinD ke liye --privileged kyun zaroori hai? A: Kyunke inner Docker daemon ko kernel features (namespaces, cgroups, storage driver mounts) chahiye hote hain jo normal container me blocked hote hain.

Q3: CI pipelines me DinD socket mount se behtar kyun samjha jata hai? A: Har job ko apna isolated daemon aur clean image cache milta hai β€” parallel builds ek dusre se nahi takrate aur host ka Docker clean rehta hai.

Q4: --privileged ka sab se bara risk kya hai, aur ek safer alternative batao? A: Privileged container lagbhag saari isolation kho deta hai β€” compromise hone par host tak access mumkin hai. Safer alternative: rootless DinD (docker:dind-rootless), remote builder, ya Kubernetes CI me Kaniko/BuildKit.

πŸ”œ Next Week

Week 14 me hum poori team ke liye same dev environment banayenge β€” compose override files, live code reload aur seeded databases ke sath. ⏭️


Edit page
Share this post on:

Previous Post
Week 14: Team Dev Environments & Parity
Next Post
Week 12: Resilience Patterns β€” Circuit Breakers