Conversation
- working dazzle tests for linux/amd64 platform - auto-detect TTY for buildkit - dazzle init - consume chunk env/cfg for buildkit runner tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a complete rewrite of dazzle. It is deliberately incompatible with the previous version. With this rewrite dazzle uses buildkit to build the individual chunks, and combines them by producing OCI manifests and configurations directly. Using buildkit/containerd's resolver provides several benefits:
There's a release build for this version here: https://github.com/gitpod-io/dazzle/releases/tag/v0.1.0
New project format
In addition, this rewrite changes the format of a dazzle project. Previously everything was contained within a single
Dockerfileand now is split across several folders. See here for how building workspace-full (and variants) looks like with this rewrite. Again, there are several benefits to this method:Note: thanks to these more flexible means of combination, we can now build all workspace-full variants (including workspace-base) in dazzle itself. This significantly speeds up workspace-image builds.
Environment Variables
This version also sports more flexible merging abilities for environment variables. For each env var one can configure how they are to be merged if multiple chunks define the same variable. The following modes are available:
mergewhich appends all values separated by:merge-uniquewhich is likemerge, except that only appends unique values, but in random orderuse-firstuses the first value we've seenuse-lastuses the last value we've seenTests
Tests work much the same way as they have before.
Image Combination Prologue
There is one feature that's currently missing, and I'm not sure we actually need it: the prologue. The old dazzle could perform some operations on the merged image, the new version of dazzle can no longer do this.