Houdini 20 and connector 200.0.1 error in docker container

Omniverse Connections & Data Exchange Omniverse Connectors
1

Hi

We’ve had v100 running in a docker container in the past but as we’re trying to use v200.0.1 of the houdini connector. We’re getting errors which we didnt run into in v100.

hython-bin crashed. FATAL ERROR: [TF_DEBUG_ENVIRONMENT_SYMBOL] multiple debug symbol definitions for ‘OMNI_USD_RESOLVER’. This is usually due to software misconfiguration, such as multiple versions of the same shared library loaded simultaneously in the process. Please check your build configuration.
in _Register at line 139 of /home/prisms/builder-new/WeeklyDevTools20.0/dev_tools/src/usd/usd-23.08/USD-py3.10/pxr/base/tf/debug.cpp

To get the plugin files i had a fresh linux VM installed with Houdini and i used the omniverse launcher to install the plugin. I took the files then saved them and put them into my docker container. I tested the setup by having a second fresh linux VM with houdini installed and put the plugin files into Houdini and it runs fine, it seems to be an issue with Docker it self? i’ve tried having it use the install script or using the json package file i put my self (never at the same time) to point to the plugin but no success.
Is there a location or system i can run in docker which would have the plugin install it self similar to that of the omniverse launcher?

Thanks

2

I wasn’t aware of this website
https://enterprise.launcher.omniverse.nvidia.com/exchange/connector/houdini-connector?text=houdini
You can download the plugin zip file from there. The problem i was facing was that the symlinks that get created when the plugin get’s unzipped by the launcher were naturally breaking as paths were different. As i now have the zip file for the plugin it self, the symlinks now extract and deploy correctly.

3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.