ISAAC Gym does not run in headless mode on ISAAC SIM on aws

Dear forum members,

I set-up a ISAAC SIM in a docker container on an instance on AWS using the installation tutorial in the documentation.
3. Deploy to Cloud — Omniverse Robotics documentation

When running the app in the headless mode using: ./runheadless.native.sh
I get the following errors:

2022-09-08 13:09:45 [19,435ms] [Error] [carb.windowing-glfw.plugin] GLFW initialization failed.                                                                             2022-09-08 13:09:45 [19,435ms] [Error] [carb] Failed to startup plugin carb.windowing-glfw.plugin (interfaces: [carb::windowing::IGLContext v1.0],[carb::windowing::IWindowing v1.3]) (impl: carb.windowing-glfw.plugin)                                                                                                                                2022-09-08 13:09:45 [19,437ms] [Error] [carb.windowing-glfw.plugin] GLFW initialization failed.                                                                             2022-09-08 13:09:45 [19,437ms] [Error] [carb] Failed to startup plugin carb.windowing-glfw.plugin (interfaces: [carb::windowing::IGLContext v1.0],[carb::windowing::IWindowing v1.3]) (impl: carb.windowing-glfw.plugin)                                                                                                                                2022-09-08 13:09:45 [19,439ms] [Error] [carb.scripting-python.plugin] RuntimeError: Failed to acquire interface: carb::windowing::IWindowing (pluginName: nullptr)                                                                                                                                                                                      At:                                                                                                                                                                           /isaac-sim/kit/exts/omni.kit.window.cursor/omni/kit/window/cursor/cursor.py(27): on_startup                                                                                 /isaac-sim/kit/plugins/bindings-python/omni/ext/impl/_internal.py(135): _startup_ext                                                                                        /isaac-sim/kit/plugins/bindings-python/carb/profiler/__init__.py(80): wrapper                                                                                               /isaac-sim/kit/plugins/bindings-python/omni/ext/impl/_internal.py(186): startup                                                                                             /isaac-sim/kit/plugins/bindings-python/omni/ext/impl/_internal.py(268): startup_extension                                                                                   PythonExtension.cpp::startup()(2): <module>                                                                                                                                                                                                                                                                                                           2022-09-08 13:09:45 [19,439ms] [Error] [omni.ext.plugin] [ext: omni.kit.window.cursor-1.0.1] Failed to startup python extension.

When trying to start the isaac-gym extension, the app crashes and i get the following error:

[133.956s] [ext: omni.kit.registry.nucleus-0.0.0] startup                                                                                                                   running process: ['/isaac-sim/kit/kit', '/isaac-sim/apps/omni.isaac.sim.python.gym.headless.kit', '--ext-folder', '/isaac-sim/kit/extsPhysics', '--ext-folder', '/isaac-sim/exts', '--ext-folder', '/isaac-sim/apps']                                                                                                                                   Omniverse Kit cannot be run as the root user without the --allow-root flag.                                                                                                 Running as root should not be necessary under most circumstances.

I looked up, the error message, but could not find the files, being used in other solutions to a similar problem.

Is it, because the Nucleus is not running on the same instance, or do I need to make other configurations?

Thanks in advance!