Open civerachb-cpr opened 4 months ago
Aha! I solved my own problem. For anyone in the future who finds this, the Python crash appears to be related to SHM. Modifying my docker container's DDS profile to
<?xml version="1.0" encoding="UTF-8" ?>
<dds>
<profiles xmlns="http://www.eprosima.com/XMLSchemas/fastRTPS_Profiles">
<transport_descriptors>
<transport_descriptor>
<transport_id>CustomUdpTransport</transport_id>
<type>UDPv4</type>
</transport_descriptor>
</transport_descriptors>
<participant profile_name="turtlebot4_republisher_profile" is_default_profile="true">
<rtps>
<userTransports>
<transport_id>CustomUdpTransport</transport_id>
<initialPeersList>
<locator>
<udpv4>
<address>127.0.0.1</address>
</udpv4>
<udpv4>
<address>192.168.186.2</address>
</udpv4>
</locator>
</initialPeersList>
</userTransports>
<useBuiltinTransports>false</useBuiltinTransports>
</rtps>
</participant>
</profiles>
</dds>
appears to have fixed the issue; I'm now able to echo topics without crashing.
EDIT
After rebuilding the containers, it turns out the above did not actually fix the issue; I'm still seeing the exact same Python error when trying to echo a topic inside the container, even with the DDS profile above.
I've got a Humble docker container that's raising
xmlrpc.client.ResponseError
errors when I try to echo topics. It doesn't make any difference if the topics are published inside or outside the container.This started happening on July 3; prior to that topics appeared to echo correctly. I see there was a new release on or around July 2, so depending on the exact timing of when that release was made available and when I built the first image to exhibit this error it could be related? I definitely was able to echo topics properly with images made early in the morning (EDT) on July 2, but since pulling the latest
ros:humble
image things seem to have broken.Exception details:
The
/test
topic above was generated withros2 topic pub
inside the container:Docker build files, and relevant files included in volumes are below:
Dockerfile:
I've tried another image that does not include the testing server, and it too is exhibiting the same bug when I try to echo topics inside the container. So it's not the presence of the testing server that's causing this.
build.sh
Pretty standard build for a container.
docker-compose.yml
I'm using
docker compose --profile republisher up
to start my container.config/create3.env:
config/fastrtps-repub.xml
The DDS profile is to restrict traffic from the Turtlebot4 from going anywhere other than to the Raspberry Pi the container is running on; the goal is for the Pi to be republishing all of the Create3 topics/services/actions using this container.