IGN Transport comms between docker containers. Can I force the Bind ports?
Hi I've encountered a recent breakage when trying to communicate between a 18.04 docker container running ign-blueprint and a 16.04 host system with ros-kinetic and Gazebo11.
A few months ago I was able to set the IGN_PARTITION to a common name and this was sufficient to ensure that ignition transport topics could published and subscribed between these environments. However this is no longer the case. The IGN envrionment variables in the 18.04 docker container are:
IGN_LAUNCH_CONFIG_PATH=/home/developer/subt_ws/install/share/subt_ign/launch
IGN_GAZEBO_RESOURCE_PATH=/home/developer/subt_ws/install/share/subt_ign/worlds
IGN_PARTITION=sim
IGN_VERBOSE=1
IGN_IP=10.4.41.228
IGN_LAUNCH_PLUGIN_PATH=/home/developer/subt_ws/install/lib
And on the 16.04 host system:
IGN_VERBOSE=1
IGN_LAUNCH_PLUGIN_PATH=/home/developer/subt_ws/install/lib
IGN_IP=10.4.41.228
IGN_PARTITION=sim
Within the docker container the ignition bridges I am using are working. However I have noted with the transport on the verobse setting that the pub/sub and client/server ports are different. In docker container
Current host address: 10.4.41.228
Process UUID: 8233b3b2-2ffa-4d9e-b2a7-1d77ec18080c
Bind at: [tcp://10.4.41.228:42641] for pub/sub
Bind at: [tcp://10.4.41.228:46545] for srv. calls
On Host System:
Current host address: 10.4.41.228
Process UUID: 0f070fe7-98a1-4a8b-af20-5f11905b8a37
Bind at: [tcp://10.4.41.228:34671] for pub/sub
Bind at: [tcp://10.4.41.228:38209] for control
Bind at: [tcp://10.4.41.228:44359] for srv. calls
Identity for receiving srv. requests: [477b3498-7ef3-4fa0-a04c-5d58c0ab5696]
Identity for receiving srv. responses: [03f87423-4618-466d-a34b-f28cce2be5b0]
I also had problems using ign topic -e -t /topic_foo, there was no output, but was able to have the bridge work when run in the same session.