-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YETUS-1230. hadolint is not executable on arm64 #309
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use
COPY/ADD --link
in place of this embedded curl command? I think it caches better, but requiresdocker/dockerfile:1.4
or later. https://docs.docker.com/engine/reference/builder/#copy---linkThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably worth experimenting with now.
There were a few evolutions.
ADD
+RUN
would generate 2 layers instead of a singleRUN
layer. Those extra layers added up in the final image making it much bigger than necessary. When we only built images for x86, there were checksums for all of the files. With multi-arch + multi-stage builds, those two problems are mostly non-existent now.Caching should be pretty good withe multi-stage builds so long as
yetusbase
doesn't change. If it does change, in some cases one really wants to rebuild that stage anyway. But that wouldn't have an impact onADD
anyway.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, why not just add an elif or whatever statement here rather do two downloads and have to figure out which hadolint should be in place later on in the Dockerfile?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docker's runtime prunes the execution graph such that the download only happens for the architecture target that is being built. If you're building a multi-articture image, both binaries are downloaded and both are used by independent copies of the subsequent step. That step is only defined once (keeping things DRY) and the downloaded binaries are both cached, which eases developer pain. I agree that it adds to layer accumulation.