An image layer is an immutable filesystem change within a layered container image. OCI images can cache and reuse unchanged layers during builds, while registries store and transfer images by layer. section 3.2.1
Image layers affect container-image performance in two workflows:
- Builds can reuse unchanged layers, reducing repeated work. section 3.2.1
- Pulls download only changed layers, saving time and bandwidth across application instances. section 3.2.1
- Layer contents and ordering matter: placing frequently changing application code with stable dependencies can force unnecessarily large rebuilds. section 3.2.1
Java application artifact
Copying a Java JAR containing application code, libraries, and dependencies into the top layer means that adding one HTTP endpoint rebuilds the whole layer, even when dependencies remain unchanged. section 3.2.1






