When creating custom Sitecore images, what should you do with built outputs and assets?

When creating custom Sitecore images, it is essential to layer built outputs and assets onto the base Sitecore runtime images for several reasons. Layering allows you to take advantage of the existing stability and performance optimizations of the base images while customizing the environment to your specific needs. By utilizing the existing runtime images, you ensure that your custom images inherit the necessary configurations and dependencies needed for a successful Sitecore application.

Additionally, including a runtime Dockerfile for each container is a best practice that facilitates the build and deployment process. A Dockerfile allows you to define how to construct your custom image, detailing the steps required to copy your built outputs and assets, install dependencies, and set up necessary configurations. This enables you to maintain version control, replicate environments, and streamline the deployment process in a consistent manner. Incorporating both layering built outputs onto the base images and creating a runtime Dockerfile provides a comprehensive approach to building customized Sitecore images that are efficient, manageable, and aligned with best practices in containerization.