We’re trying to establish a connection between the ROS core inside of the NRP container and another machine on the same network as the NRP host. The concrete setup is that we have two machines: an NRP host machine running the NRP docker containers and a separate machine that’s running a ROS node. The second machine will have to interact with ROS (ROS core) in the NRP host machine.
When we run the NRP script out-of-the-box, it’ll create a local network ‘nrpnet’. Meaning, that the ROS ports will be inaccessible from outside that network. So far we’ve modified the NRP script to simply run the NRP containers on the host network (–net=host), and it works. But we’re not sure whether that’s a sustainable solution.
Specific port mapping is also not an option, because ROS uses dynamic port allocation.
Specifically we have two questions:
- Are there better ways to establish the connection between the NRP host and the ROS node than setting --net=host?
- If not, could this somehow be integrated into the NRP script? Possibly with a flag or similar?
Thanks a lot for your help,
PS. This is close to the question asked by Jacques (Connect docker container with ROS on host). Only, we’re trying to connect to ROS from another machine.