Docker Tutorials: Engine v29.x — Guide to Major Changes, Architecture & Migration

📌 Introduction

Docker remains the most popular container runtime for developers and sysadmins, but starting from Docker Engine v29.x, significant internal architecture changes have emerged. These changes impact how container images are stored, where layered filesystems exist, and how Docker integrates with its underlying containerd runtime.

This guide covers:

• Major differences between Docker ≤28 and v29+
• Internal storage layout changes
• Impacts on developers and administrators
• How to inspect image and container layers now
• Migration and compatibility guidance

🧱 Docker Architecture — Before v29

In earlier Docker versions (up to v28.x):

🆕 What’s New in Docker 29.x?

🎯 Key Changes

🔍 Storage Layout – Then vs Now

Before Docker v29:

/var/lib/docker/
  ├── overlay2/               # Data for layers and containers
  ├── containers/
  ├── image/
  │    └── overlay2/
  │         └── layerdb/
Code language: PHP (php)

Docker v29 and after:

/var/lib/docker/
  ├── rootfs/overlayfs/       # Merged rootfs for active containers
  ├── containers/
  ├── volumes/

# Image layers are now here:
  
/var/lib/containerd/
  ├── io.containerd.content.v1.content/
  ├── io.containerd.snapshotter.v1.overlayfs/
  │    └── snapshots/<id>/fs    # Physical image layer content
Code language: PHP (php)

🧠 Developer Notes

• Image Developers: Image layers are now under /var/lib/containerd/... — not /var/lib/docker/....
• Container Debuggers: Live container filesystems are still under /var/lib/docker/rootfs/....
• Storage Tools: Tools that scanned /var/lib/docker/image/ will need updates for Docker 29+.
• DevOps Pipelines: Docker API version must be ≥1.44 — update older SDKs or CI automation.
• Advanced Users: Use ctr or nerdctl to inspect containerd-managed snapshots.

🛠️ Practical Examples

🧾 Retrieve Image Snapshot Info via ctr:

ctr -n moby images ls | grep <image>
ctr -n moby image info docker.io/<image>:tag
ctr -n moby snapshots ls
Code language: HTML, XML (xml)

🗂️ View Image Layer Contents:

cd /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/<id>/fs
ls -al
Code language: JavaScript (javascript)

🧾 Inspect Container RootFS:

cd /var/lib/docker/rootfs/overlayfs/<container-id>/
ls -al
Code language: JavaScript (javascript)

⚠️ Impact and Migration Guidance

• Existing Hosts:
  • Docker v29 does not force migration — your existing overlay2/aufs data is retained.
  • Plan carefully if manually moving to containerd storage backend.
• New Installations:
  • Automatically use containerd image store and snapshotter — follow the new paths.
• Tools & Plugins:
  • Ensure compatibility with API 1.44+ and the containerd layout.
  • Update scanning, backup, and forensic tools accordingly.
• CI/CD Agents:
  • Ensure Docker SDK versions, client libraries, and API calls are upgraded.

🧭 Conclusion

Docker v29 is a major evolutionary jump, aligning Docker more deeply with containerd’s architecture, cleaning up storage models, modernizing networking, and improving modularity.

This change benefits the ecosystem — but requires awareness and adaptation from developers, administrators, and tool maintainers.

Key paths to remember:

• Image Layers:
  /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/<snapshot-id>/fs
• Container Filesystems:
  /var/lib/docker/rootfs/overlayfs/<container-id>/

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.