Multistage dockerfile example #571
Merged
Conversation
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
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 slight elaboration on Jason's initial work.
Moving the COPY src/ src/ from the build stage to the runtime stage enables near instantaneous builds for source-only updates.
The
RUN mkdir /keripy/srcin the build layer enables the setup.py and requirements.txt to be able to fully execute.Building from scratch, or with no cache, a
linux/amd64image on my Mac takes about 25 minutes. This Dockerfile enables me to have a build that is less than 5 seconds when there are source only changes. However, dependency changes still require a full rebuild.