Conversation
Member
Author
|
I experimented with some changes to the base-template build pipeline before deciding it's too complicated and too far out of scope. The failed checks (the base image build and release job) are unrelated as long as pytorch 2.6 will release. |
Yhlong00
approved these changes
Apr 14, 2025
When I can use it in runpod? |
|
When will this be merged? |
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
4 participants
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.
By user request, I've added a PyTorch 2.6.0 image.
This PR also adds version pinning to torch dependencies for all PyTorch containers. Previously, these containers weren't actually the version on their names, rather whatever the latest
torchwas at the time of build/release.Closes #84, didn't recognize this was already open. I'll update my branch to include credit to the author.