![]() ![]() ![]() chunks that can be strictly separated, then this might for you.įor example, if you're building an image that serves as a collection of tools, the layer hierarchy imposed by regular builds doesn't fit so well. If however you are building images which consist of a lot of independent "concerns", i.e. For example, if you're packing your service/app/software/unicorn you're probably better of with a regular Docker image build and well established means for optimizing that one (think multi-stage builds, proper layer ordering). run tests against images: to ensure that an image is capable of what we think it should be - especially after merging - dazzle supports simple tests and assertions that run against Docker images.merge layers into one image: dazzle can merge multiple OCI images/chunks (not just those built using dazzle) by building a new manifest and image config that pulls the layers/DiffIDs from the individual chunks and the base image they were built from.After each chunk image build dazzle will remove the base image layer from that image, leaving just the layers that were produced by the chunk Dockerfile. ![]() Dazzle can build the base image (built from base/Dockerfile), as well as the chunk images. All of them share the same base image using a special build argument $. These chunk images are built independently of each other. build independent layer chunks: in a dazzle project there's a chunks/ folder which contains individual Dockerfiles (e.g.It is also about 5x faster, more reliable and less hacky. Its goal is to build independent layers where a change to one layer does not invalidate the ones sitting "above" it.īeware Recently the format for dazzle builds was changed, moving from a single Dockerfile to one per "chunk"/layer. Dazzle is a rather experimental Docker/OCI image builder. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |