# Cannot list zed\_wrapper nodes or components in localhost but they are listable in remote hosts. 

**URL:** <https://community.stereolabs.com/t/cannot-list-zed-wrapper-nodes-or-components-in-localhost-but-they-are-listable-in-remote-hosts/9843>\
**Category:** Software\
**Tags:** docker, jetson\
**Created:** [September 9, 2025, 7:18am UTC](https://community.stereolabs.com/t/cannot-list-zed-wrapper-nodes-or-components-in-localhost-but-they-are-listable-in-remote-hosts/9843 "2025-09-09T07:18:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![matialmar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/matialmar/32/4971_2.png) [@matialmar](https://community.stereolabs.com/u/matialmar)\
**Post date:** [September 9, 2025, 7:18am UTC](https://community.stereolabs.com/t/cannot-list-zed-wrapper-nodes-or-components-in-localhost-but-they-are-listable-in-remote-hosts/9843/1 "2025-09-09T07:18:18Z")

</div>

Hello,

I am using the `zed_ros2_wrapper` to bring up the zed camera and use the depth map in another docker for post-processing.

My configuration is the following:

- Jetson: AGX Orin, JetPack 6.0
  - This is the localhost

- Camera: ZED 2
- ROS: Humble
- ZED: SDK 5.0
- RMW: rmw\_fastrtps\_cpp
- Environment: Docker container
- Remote host: Ubuntu 20.04 container with ROS2 humble and CUDA support
- All the containers are running using `--network host` and `--ipc host`

What is running properly:

- `zed_ros2_wrapper` and `zed_ros2_examples`in the dockerized environment:
  - Builds correctly
  - Executes correctly

- In a **remote**  **docker container** (the post-processing docker) with our software to subscribe to the topics and receive the depth map.
  - 
    - `ros2 component list` → zed components
    - `ros2 node list` → zed nodes
    - `ros2 topic list`→ zed topics
    - Subscribing to topic → successful and receiving data

- Using `zed_display_rviz2` in the same docker image is successful both local and remote.

Issues we are facing:

- **Inside the docker** where `zed_ros2_wrapper` is running (in the Jetson Orin) executing the following commands delivers the following outputs:
  - `ros2 component list` → empty output
  - `ros2 node list` → empty output
  - `ros2 topic list`→ zed topics
  - Subscribing to topic using `rviz2` → successful but without any data
  - Subscribing to topic using a custom node → successful but without any data

- Using another ROS2 docker such as Isaac ROS or dustynv’s ros-humble
  - Same results as above.

- Using RVIZ2 both in the zed wrapper container or another outputs `no tf data, fixed frame map does not exist`

Any help is much appreciated!

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [September 9, 2025, 9:49am UTC](https://community.stereolabs.com/t/cannot-list-zed-wrapper-nodes-or-components-in-localhost-but-they-are-listable-in-remote-hosts/9843/2 "2025-09-09T09:49:29Z")

</div>

Hi @matialmar  
Welcome to the [StereoLabs](https://www.stereolabs.com/) community.

I recommend you read the content of the Docker README file in the ZED ROS2 Wrapper GitHub repository:

> <https://github.com/stereolabs/zed-ros2-wrapper/blob/master/docker/README.md#run-the-docker-image>

[Please also check that the `ROS_DOMAIN_ID` is the same for all the environments.](https://www.stereolabs.com/docs/ros2/dds_and_network_tuning#ros-domain)

I recommend you also read this guide: [DDS Middleware and Network tuning - Stereolabs](https://www.stereolabs.com/docs/ros2/dds_and_network_tuning)

---

<div class="post-metadata">

**Author:** ![matialmar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/matialmar/32/4971_2.png) [@matialmar](https://community.stereolabs.com/u/matialmar)\
**Post date:** [September 9, 2025, 1:37pm UTC](https://community.stereolabs.com/t/cannot-list-zed-wrapper-nodes-or-components-in-localhost-but-they-are-listable-in-remote-hosts/9843/3 "2025-09-09T13:37:39Z")

</div>

Thank you Myzhar for your quick response!

I checked that ROS\_DOMAIN\_ID is the same for all nodes. (ROS\_DOMAIN\_ID = 0)  
After tinkering with ROS and docker I found the solution to my problem. It is not a ZED SDK problem but a FastDDS one.

Using the ros pub/sub example in different containers I encountered the same issue. After just removing the `–network host` option I was able to discover and communicate between the nodes in the different containers. Yet now I cannot use in a remote node, so after searching the web a found this **[Stack Exchange](https://robotics.stackexchange.com/questions/98161/ros2-foxy-nodes-cant-communicate-through-docker-container-border) post** wich explained the following:

> Using `--net=host` implies both DDS participants believe they are in the same machine and they try to communicate using SharedMemory instead of UDP. Fast-DDS team will work in to implement a mechanism to detect this kind of situation.

However mapping `/dev/shm` into the docker container while using `–network host` **did not work.** Which is rare because just removing the `–network host` worked perfectly in the local container, the reason for this behaviour is yet unknown to me.

The comment bellow pointed about setting the FastDDS transport to UDP

> Setting `FASTDDS_BUILTIN_TRANSPORTS=UDPv4` can be helpful.

Using this as an environment variable did the trick and allowed me to use them both in local containers and remote ones. But i guess at the expense of losing the performance boost of using shared memory.

I hope someone finds this useful if they are in the same use case.
