Add libtbb2 to gpu.Dockerfile #1779
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
libtbb2 is need for gpu docker container see nodeodm bug OpenDroneMap#219
|
Nice, this needs confirmation that it works correctly with CUDA before merging. |
|
Tested and builds and runs fine. However this bug only seemed to appear when using webODM/nodeODM, as it ran fine using ODM directly, so not sure if fixing it here will solve the downstream issue in NodeODM? |
|
Thanks for testing and confirming! It might be an issue with cgroups and docker-compose, in which case perhaps it's an issue with how WebODM brings the node online. I'll merge this for now since it should fix ODM. Thank you! |
|
ok, once the nodeODM image is built I'll test it |
|
tested with odm_data_aukerman and it's now working on nvidia GPU in webODM |
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.
libtbb2 is need for gpu docker container
see nodeodm bug #219