What is a drawback of having too many layers in a container image?

What is a drawback of having too many layers in a container image?

• A. Reduces image portability
• B. Potential inefficiencies in image size and build times
• C. Increases security
• D. Improves caching efficiency

Answer: (B)

Having many layers in a container image tends to create more overhead for storage, transfer, and build time. Each layer is stored as its own tarball with metadata, so piling up layers adds up not just in the final image size but also in the work needed to create and assemble them during a build and to pull or push the image. When you add more layers, small changes can invalidate caches for subsequent layers, leading to longer build times and less efficient use of caching. That’s why combining commands (RUN commands, for example) and using multi-stage builds to keep the final image lean helps keep both size and build time under control. Portability isn’t inherently reduced by the number of layers, since the image format remains the same as long as the runtime supports it. Security isn’t automatically improved by more layers; while scanning can occur per layer, the mere count of layers doesn’t make the image more secure. Caching efficiency isn’t guaranteed to improve with many layers; in fact, it can suffer from cache misses if changes ripple through many layers.

Having many layers in a container image tends to create more overhead for storage, transfer, and build time. Each layer is stored as its own tarball with metadata, so piling up layers adds up not just in the final image size but also in the work needed to create and assemble them during a build and to pull or push the image. When you add more layers, small changes can invalidate caches for subsequent layers, leading to longer build times and less efficient use of caching. That’s why combining commands (RUN commands, for example) and using multi-stage builds to keep the final image lean helps keep both size and build time under control.

Portability isn’t inherently reduced by the number of layers, since the image format remains the same as long as the runtime supports it. Security isn’t automatically improved by more layers; while scanning can occur per layer, the mere count of layers doesn’t make the image more secure. Caching efficiency isn’t guaranteed to improve with many layers; in fact, it can suffer from cache misses if changes ripple through many layers.