Multi-layer Container Image Support - May 14 2025

Hello, 

TL;DR: Chainguard Container Images will soon support multi-layers

What is changing and why?

Historically, Chainguard Containers built with our apko tool have utilized a single-layer approach. This offered simplicity and clarity, ensuring the entire filesystem was contained in one unit. However, as our image catalog and customer usage have grown, we recognized the limitations of this model especially for large container images such as our AI Images.

We are now adopting a multi-layer strategy, so we can ensure that when you update a Chainguard container image, you only need to pull the specific layers that contain changes.

We are updating all of our developer tier images to have multi-layer support today.

On May 28, 2025, we will be rolling these multi-layer container images out to all customers.

How will this affect me?

This change will allow for faster pull times of container images, especially for large container images. The on-disk storage footprint is also lower because multiple images can share things.

What do I need to do?

No action is required from you. If you use any of the developer tier images, and notice any issues, reach out to support.chainguard.dev and we’ll be able to quickly revert the changes. We will provide another update when the changes have been rolled out across your registry. 

Need help or have more questions?

We're here for you. Just drop us a line at support.chainguard.dev and we’ll be happy to help.

Your friends at Chainguard Team