Available ports in solution docker?

Issue #199 resolved
Martin Dlouhy created an issue

What ports are allowed in solution docker? In particular can I use port 8000 and 8123, which are currently hardcoded in our code? The addresses are and

Thanks a lot


p.s. they are blocked it could be the reason why it works locally but not on AWS(?)

Comments (11)

  1. Nate Koenig

    Ports are not blocked on the container running your solution. The addresses and ports you listed will work on cloudsim.

  2. Martin Dlouhy reporter

    Thank you Nate. The simulation ver1 yesterday (robotika, simple_tunnel_02, 83e49d56-2d53-4818-a4d5-aac8a2a6171b) terminated as ver0, i.e. there was probably no command sent from Python code. On which IP address is ROS master? I use "ros_master_uri": "" - could this be a problem? In “roslaunch-sim-83e49d56-2d53-4818-a4d5-aac8a2a6171b-comms-rbt1-52.log” I see [roslaunch][INFO] 2019-09-23 14:24:26,046: master.is_running[]??


  3. Arthur Schang

    You should not explicitly use localhost unless you are able to force localhost as the ROS_IP and ROS_MASTER_URI. On the Cloudsim, it is dynamically set to an IP that is not localhost so you will need to check the environmental variables $ROS_IP and $ROS_MASTER_URI.

  4. Arthur Schang

    Yes, if you want to hook into the ROS Master already running, you will need to use those variables defined environmentally. Technically you can run multiple ROS Masters on the same machine on different ports but I don’t think that’s what you’re trying to do here.

  5. Martin Dlouhy reporter

    p.s. it looks like that only ROS_MASTER_URI is defined in local solution docker:

    developer@gpu-desktop:~/subt_solution$ set | grep -e ROS_IP -e ROS_MASTER_URI -e ROS_HOSTNAME

  6. Arthur Schang

    Both ROS_MASTER_URI and ROS_IP are defined in Cloudsim on the competitor instance. I checked it this morning.

  7. Martin Dlouhy reporter


    thanks it helped a bit - but based on results on “Simple Tunnel 02” (4 teams with 0 points) we all have maybe similar issue??

    New master URI and ROS_PI helped one step forward (robotika, c6783f3d-ca90-409a-8fe5-ad34c37f4097) at least I now see OSGAR subscription:

    [rosmaster.master][INFO] 2019-09-24 10:05:48,127: +SUB [/X2/imu/data] /osgar_node
    [rosmaster.master][INFO] 2019-09-24 10:05:48,144: +SUB [/X2/front_scan] /osgar_node
    [rosmaster.master][INFO] 2019-09-24 10:05:48,160: +SUB [/X2/front/image_raw/compressed] /osgar_node
    [rosmaster.master][INFO] 2019-09-24 10:05:48,177: +SUB [/X2/odom] /osgar_node
    [rosmaster.master][INFO] 2019-09-24 10:05:48,192: +PUB [/X2/cmd_vel] /osgar_node
    [rosmaster.master][INFO] 2019-09-24 10:05:48,220: publisherUpdate[/X2/cmd_vel] -> ['', '']
    [rosmaster.master][INFO] 2019-09-24 10:05:48,221: publisherUpdate[/X2/cmd_vel] -> ['', '']: sec=0.00, result=[1, '', 0] 

  8. Log in to comment