uRos node not listing

- Hardware description: Rasperry PI connected to RP2040 nano connect
- RTOS: NA
- Version or commit hash: Humble

Hello again,

I am running uROS on a RP2040 connect. As usual, for testing I am using docker which launches the micro ros agent in humble:

``
docker run -it --rm -v /dev:/dev --privileged --net=host microros/micro-ros-agent:humble serial --dev /dev/ttyACM0 -v4
``

Everything works fine on my pc. When I go open a new bash on the image I can display the uros node and topic. I can display the contents of the message.

Then I connected my RP2040 to an embedded computer with Ubuntu server 22, Ros2 Humble. The problem is that the launch process seems to go well, I set -v5 and I see a lot of :

```
[1673362828.144831] debug | DataWriter.cpp | write | [** <> **] | client_key: 0x00000000, len: 120
[1673362828.247510] debug | SerialAgentLinux.cpp | recv_message | [==>> SER <<==] | client_key: 0x701B8528, len: 132
[1673362828.247738] debug | DataWriter.cpp | write | [** <> **] | client_key: 0x00000000, len: 120
[1673362828.247881] debug | SerialAgentLinux.cpp | recv_message | [==>> SER <<==] | client_key: 0x701B8528, len: 16
```

But unfortunately and after launching the uros agent, the commands for listing the topics and the nodes do not display anything.

``
$ros2 node list
$ros2 topic list
/parameter_events
/rosout
``

Any suggestions would be greatly appreciated.

Start by reproducing the reported setup with the micro-ROS Agent Docker command on Ubuntu Server 22 and compare it with the working PC setup. Check the `ros2 node list` and `ros2 topic list` results while reviewing the agent's verbose output; done means the RP2040 node and its topics appear in the ROS 2 graph.

Written by the indexing model from the issue text.