As part of our continuous improvements to Devtron’s CI/CD capabilities, we’re preparing for a Docker engine upgrade to version 27. This upgrade introduces performance enhancements and build system improvements.

Why Docker v27?

Docker v27 introduces foundational changes in how builds are managed, streamlining CI workflows:

• BuildKit is now the default backend – No manual configuration needed; all builds now run through the faster and more robust BuildKit engine.

• Buildx is now the default build driver – All CI builds will automatically support multi-architecture image creation (like amd64 and arm64), remote caching, and flexible output options without requiring explicit setup.

• Improved caching behavior – Layer caching is more efficient and works seamlessly with cross-platform builds.

• OCI-compliant output support – Docker images are now more portable and registry-friendly.

What’s Changing?

Devtron’s CI infrastructure will adopt Docker v27 across the board, using the new BuildKit + Buildx stack as the default for all image builds.

Key Benefits

• Out of the box support for Multi-Architecture Builds
  No extra setup required - arm64, amd64, and other architecture images will be supported out of the box.

• Smarter Build Caching
  Better reuse of image layers, reducing cache size and CI run-time.

• Enhanced CI Pod Metadata
  Improved labeling for CI pods in Kubernetes for easier monitoring and debugging.
  
  

Cache reset Alert and Precautionary action Required

Docker v27 is incompatible with older cache versions and hence this upgrade will reset existing build caches. Pipelines relying on old cache may face initial delays or failures.

Run a CI build with “Ignore Cache” ticked before this upgrade to verify that your CI pipelines work fine without utilizing the old cache.

Please refer to the short GIF below to see how to do it.