Closed fri-K closed 1 month ago
NodeODM started as docker container is failing because of lack of library
[INFO] Writing MVS Textured file in: /var/www/data/0fac5ca1-719a-4e71-b68f-06ac94092e3e/odm_texturing_25d/odm_textured_model_geo.obj [INFO] running "/code/SuperBuild/install/bin/texrecon" "/var/www/data/0fac5ca1-719a-4e71-b68f-06ac94092e3e/opensfm/undistorted/reconstruction.nvm" "/var/www/data/0fac5ca1-719a-4e71-b68f-06ac94092e3e/odm_meshing/odm_25dmesh.ply" "/var/www/data/0fac5ca1-719a-4e71-b68f-06ac94092e3e/odm_texturing_25d/odm_textured_model_geo" -d gmi -o gauss_clamping -t none --no_intermediate_results --nadir_mode --max_texture_size=8192 /code/SuperBuild/install/bin/texrecon: error while loading shared libraries: libtbb.so.2: cannot open shared object file: No such file or directory
NodeODM should proceed without issues
Start new task from WebODM and it fails every time
Workaround is to install it manually:
docker exec -it --user root NODE_ODM_HASH /bin/bash -c 'apt update && apt install libtbb2 -y'
It's a new issue, previous images were running fine, new image id is: 8055b7f678a5
Hi, problem is fixed with Docker image 334a1e54515d, you can close the ticket. Thanks for you support and this great software
Or maybe I can close it by myself?
What is the problem?
NodeODM started as docker container is failing because of lack of library
What should be the expected behaviour?
NodeODM should proceed without issues
How can we reproduce this? (What steps did you do to trigger the problem? Be detailed)
Start new task from WebODM and it fails every time
Workaround is to install it manually:
docker exec -it --user root NODE_ODM_HASH /bin/bash -c 'apt update && apt install libtbb2 -y'
It's a new issue, previous images were running fine, new image id is: 8055b7f678a5