Purge the pip cache after installing torch #143
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
panchalhp-db
approved these changes
Nov 1, 2023
ygong1
approved these changes
Nov 1, 2023
|
@mdagost the docker images on dockerhub have been updated with this change: https://hub.docker.com/layers/databricksruntime/gpu-pytorch/cuda11.8/images/sha256-4fd825414b78dc352602f427537cae086126ad1cf47edcf793ef196d2b958ff2 and the image size is down to 4.87 Gb. Thank you again for discovering the issue and helping fix it as well! |
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.
The pytorch GPU container is quite large, and building off of it is causing timeouts on Databricks. See #142 . Purging the pip cache after torch install seems to save about 2 GB on the image size. Looks like this is done here in the venv image but not done after the torch installs. This PR fixes that.