feat: allow specifying Kaniko targets for multi-stage dockerfiles#436
Open
hamishc wants to merge 3 commits intocoder:mainfrom
Open
feat: allow specifying Kaniko targets for multi-stage dockerfiles#436hamishc wants to merge 3 commits intocoder:mainfrom
hamishc wants to merge 3 commits intocoder:mainfrom
Conversation
added 3 commits
December 16, 2024 22:20
…tion to skip building unused layers
Author
|
Any chance getting this reviewed sometime soon? This is blocking the adoption of coder for our org, as we rely on multi-stage dockerfiles and devcontainers for most of our repositories. |
|
I would also love to get this. |
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.
I've encountered issues with large multi-stage dockerfiles when targeting one particular stage. For example, if we have a devcontainer.json like
and a Dockerfile as the following
then running
docker run -it -v /my/repo:/workspaces/empty coder/envbuilder:latestwill result in the following errorThis is because we don't specify the build target in
KanikoOptions. Specifying this option can also substantially decrease build times, especially when combined with theSkipUnusedStagesoption - which can allow for large unused build stages to be avoided entirely.