builder-next: Set moby exporter as default#45690
Merged
thaJeztah merged 1 commit intomoby:masterfrom Jun 2, 2023
Merged
Conversation
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
rumpl
approved these changes
Jun 2, 2023
This was referenced Jun 2, 2023
neersighted
approved these changes
Jun 2, 2023
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
4 participants
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.
Building via
ImageBuildwithout exporter set made it use theimageexporter by default, which didn't go through the same special handling asmoby(settingunpackto true, sanitizing names, setting dangling image prefix).- What I did
mobyexporter by default in theImageBuild.- How I did it
- How to verify it
- Description for the changelog
containerd integration: Fix images built with
ImageBuildendpoint not created in Docker- A picture of a cute animal (not mandatory but encouraged)