Dockerfile-multiple no longer fetches pip dependencies needlessly #157
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.
Whilst developing a custom task using the Dockerfile-multiple rebuilding the Dockerfile while editing the python code also forced pip to install all dependencies again. So instead of copying the complete code path we first copy the requirements and install them using pip.
This now gives us the benefit that Docker will cache this intermediate image and only when we change the requirements.txt a rebuild is triggered. So development speed that relies on the Dockerfile-multiple is increased dramatically.