advancedDocker Registry & Image Distribution: Tagging, Versioning, Push & Pull

Why does pushing a small code change to an image that shares a base with a previous version upload quickly?

Docker registries deduplicate by layer content digest — pushing only uploads layers that don't already exist in the registry, so a small change near the top of a well-ordered Dockerfile only re-uploads the changed layer(s), not the entire image.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.

Why does pushing a small code change to an image that shares a base with a previous version upload quickly?

Next Step

Continue to Why does putting an API Gateway in front of internal microservices matter for security, not just routing?← Back to all Docker questions