Hi @Richard3D et al,
I’m running a docker container with the omnikit viewer sample app inside that needs to access a nucleus server on the local network.
I’m using OMNI_PASS and OMNI_USER with an API key to authenticate.
When starting the docker container you seem to need the --network=host option to access the nucleus but that makes the container basically appear to run directly on the host’s network. And I don’t want that.
How can the omniverse app access the nucleus with the default docker bridge configuration?
Thanks,
Robert
Actually nothing in kit needs to access Nucleus. There is no need for it. Just have your Kit file access regular files on the regular hard drive. Nucleus is now depreciated. We do not recommend it. Not unless you need a full Nucleus Enterprise Stack. So I am not sure what you are reading, but just skip Nucleus.
oh I see, thank you @Richard3D
Deprecated means support will end but it’s still available, right?
But right now I still have a lot of USD files that have reference the nucleus URL so I need to use the nucleus I have.
I don’t want to manually update those, unless there is an easier way?
If not, what do I need to configure so that the app inside the container can access the nucleus server on the same local network?
Thanks!
When you say files on Nucleus, you mean your own files or some of our Nvidia Assets? Ideally you should move away from Nucleus altogether.
yea, I have a local nucleus running right now.
I’m gonna get rid of it. Thank you