The behavior differs depending on the --net option.

[atinfinity]

Is there an already existing issue for this?

• I have searched the existing issues

Expected behavior

I set to FASTDDS_BUILTIN_TRANSPORTS=DEFAULT on docker container.
But, the behavior differs depending on the --net option.

Current behavior

option1: --net=bridge

FASTDDS_BUILTIN_TRANSPORTS	result
DEFAULT	OK
UDPv4	OK
SHM	NG

option2: --net=host

FASTDDS_BUILTIN_TRANSPORTS	result
DEFAULT	NG
UDPv4	OK
SHM	NG

Steps to reproduce

docker option

option1: --net=bridge

docker run --rm -it \
           ros:humble-ros-core \
           bash

option2: --net=host

docker run --rm -it \
           --net=host \
           ros:humble-ros-core \
           bash

command

pub

ros2 topic pub --rate 1 /turtle1/cmd_vel geometry_msgs/msg/Twist "{linear: {x: 2.0, y: 0.0, z: 0.0}, angular: {x: 0.0, y: 0.0, z: 1.8}}"

sub

ros2 topic echo /turtle1/cmd_vel

Fast DDS version/commit

• ros-humble-fastrtps 2.6.8
• ros-humble-rmw-fastrtps-cpp 6.2.6
• ros-humble-rmw-fastrtps-shared-cpp 6.2.6

Platform/Architecture

Other. Please specify in Additional context section.

Transport layer

Default configuration, UDPv4 & SHM, UDPv4, Shared Memory Transport (SHM)

Additional context

• Host OS: Ubuntu 22.04(x86_64)

XML configuration file

No response

Relevant log output

No response

Network traffic capture

No response

[JesusPoderoso]

Hi @atinfinity, thanks for using Fast DDS.
Please, refer to Fast DDS docker deployments documentation section.
I am moving this issue to the Support discussion forum according to the Fast DDS CONTRIBUTING guidelines.