-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docker example and documentation. #168
Conversation
…iners, and README for container usage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ilan-theodoro , sorry for the delay to review this.
I don't have any major comments, everything looks great.
I agree with both points, could you include them in this PR?
- Ideally, the README should be on the documentation page.
- We must create a royerlab or ultrack page on DockerHub.
Ultrack installs nvidia related libraries even when not asked, which creates bloated CPU containers.
I think using
pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cpu
before installing ultrack will install torch with CPU only
I created #171 to fix the CI issues |
@ilan-theodoro great PR. |
Some key features:
pypi
version and available torch pre-configured containers.cucim
and its dependencies on GPU supported containers.But some minor issues might be addressed:
nvidia
related libraries even when not asked, which creates bloatedCPU
containers.royerlab
orultrack
page on DockerHub.