Build with requirements.txt #43
Closed
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
Closed
4 tasks
added 7 commits
July 22, 2024 15:54
|
Tried our multi-stage build approach, and it works well! #44. I'd go for that, since its a lot simpler. |
Merged
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.
Image build failed frequently, because of heavy dependencies, mostly: Torch.
So now, I opted to use a Pytorch base image.
This works fine with a separate equirements.txt file and pip installation.
However, when I generate the requirements.txt from poetry automatically, it will create dependency on Cuda 12 instead of 11. I can't figure out how to make poetry respect the fact that torch and Cuda support are already available. Is there a way to keep in sync with the pyproject.toml/poetry.lock?