Hi,
At EUMETSAT I had found an issue when using docker universe jobs that needs IOProxy (for streaming the output or chirp communication)
If the docker bridge network is configured with anything different to 172.17.0.0/24 or the executor is not the 172.17.0.1 the IOProxy server does not work.
Hi Andres:
There is no good workaround for this today, but there is a simple fix we can make to make this more flexible. Is your bridge network always named "docker0", or might you want to use another named network?
-greg