Related to https://github.com/apache/incubator-sdap-ningesterpy/pull/9
This PR adds an option to the docker image to pick a random port for internal communication during application startup. This docker container contains 2 processes that communicate via a port. The ningesterpy process listens on a port (default 5000) for communication from the java process. A problem was noticed when deploying this to AWS Batch. Namely that AWS Batch runs containers in `network=host` mode instead of using a bridge network. This causes port conflicts when AWS tries to run multiple instances of the ningester container on the same host (because every ningesterpy instance is trying to bind to port 5000 of the host). The solution in this PR uses the feature added https://github.com/apache/incubator-sdap-ningesterpy/pull/9 that allows ningesterpy to select a random available port to bind to during startup so that multiple instances of the ningester container can run on the same host at the same time when using host networking. [ Full content available at: https://github.com/apache/incubator-sdap-ningester/pull/11 ] This message was relayed via gitbox.apache.org for [email protected]
