Simulation fails to start the first time

[agalbachicar]

Environment

• OS Version: dockerized environment
• Source or binary build? Binary build from c00d8c7

Description

• Expected behavior: the readme should just work and let the sim start flawlessly

• Actual behavior: I faced the following issues:

• In the console I can see the following errors:

  
  $ ros2 launch andino_isaac andino_isaac.launch.py

[...]

[python.sh-3] 2024-07-01 12:04:49 [10,133ms] [Error] [rtx.neuraylib.plugin] Cannot find Documents/Kit/shared directory. [python.sh-3] 2024-07-01 12:04:50 [11,742ms] [Error] [asyncio] Task exception was never retrieved [python.sh-3] future: <Task finished name='Task-174' coro=<MaterialLibraryExtension.preload_base_material_subids() done, defined at /isaac-sim/kit/exts/omni.kit.material.library/omni/kit/material/library/material_library.py:479> exception=FileNotFoundError(2, 'No such file or directory')> [python.sh-3] Traceback (most recent call last): [python.sh-3] File "/isaac-sim/kit/exts/omni.kit.material.library/omni/kit/material/library/material_library.py", line 537, in preload_base_material_subids [python.sh-3] on_complete_fn() [python.sh-3] File "/isaac-sim/kit/exts/omni.kit.material.library/omni/kit/material/library/material_library.py", line 406, in cache_built [python.sh-3] with open(self._cache_filename, 'w') as file: [python.sh-3] FileNotFoundError: [Errno 2] No such file or directory: '/isaac-sim/kit/cache/Kit/105.1/b82c1e1e/material_cache.json'

And
![image](https://github.com/Ekumen-OS/andino_isaac/assets/3825465/020dd6f3-4f26-45e3-b0ed-66d898cf26a7)

![image](https://github.com/Ekumen-OS/andino_isaac/assets/3825465/10fa9e2d-5c92-4b9f-b0b7-99fe4422f7cf)

## Steps to reproduce

1. Follow the readme.

## Extra information

Using Ubuntu 22.04 as host OS.
NVidia driver 535.183.01
RTX 4090

[agalbachicar]

After trying a suggestion from @BarceloChristian , I made it work. I did the following within the container:

sudo chown -R $USER:$GROUP /isaac_sim/

It may be only needed the chached content though. Perhaps, given that this problem occurred to some people only, we can evaluate moving this trick to a troubleshooting section.