Random ports and Dockerized Ignition

[joxoby]

There's a use-case in which we want to have an Ignition Gazebo instance running inside a Docker container and communicate with the host machine through the ignition-transport layer.

One of the problems is that the ports used by NodeShared are randomly chosen during construction. This makes it difficult to expose the ports to the host machine during the container startup, since these aren't known a priori.

Questions

• Was this use-case considered? If so, how would someone go around it?
• If it wasn't considered, are there any interests in pursuing it?

Note: docker run has the option --network=host that will mount the host network stack on the container. While this approach solves the problem above, we would prefer to avoid it (it also adds other problems when running the GUI).