Open birneamstiel opened 2 days ago
maxpolzin
commented
2 days ago What is the user id group id that you are running the things with? If they differ between in the container and the host, this is an issue in ROS2.
Do you see the topics, but don't receive messages?
birneamstiel
commented
2 days ago Thanks for your quick reply!
The user is indeed different but the user id is the same – however, even with different users the topics should be visible within the docker container, shouldn't they?
Maybe going one step back: the ros-mocap4ros2-optitrack service is supposed to publish some topics, right?
Here's what I'm trying and the resulting topics I get:
xxx@DESKTOP-PC:~/optitrack_wrapper/blox-mocap4ros2-optitrack$ id -u ${whoami}
1000
xxx@DESKTOP-PC:~/optitrack_wrapper/blox-mocap4ros2-optitrack$ docker exec -it --user 1000 blox-mocap4ros2-optitrack-ros-mocap4ros2-optitrack-1 bash
ros@docker-desktop:/$ id -u ${whoami}
1000
ros@docker-desktop:/$ source ros_entrypoint.sh
ros@docker-desktop:/$ ros2 topic list
/parameter_events
/rosout
Hey @maxpolzin, thanks for publishing this!
I have some problems setting this up. When running
docker compose upall services are launching and theros-mocap4ros2-optitrackservice seems to connect properly to the motive software (running actually on the same machine):However, I don't see any topics published, neither on the host nor when connecting to the container
ros-mocap4ros2-optitrack. I've the feeling there are some networking / connection problems where the data frames can't be retrieved within the docker containers.Did you experience similar problems when running this yourself?