[HTCondor-users] IOProxy server for docker jobs not using the default bridge network

[Andres Ayala <Andres.Ayala@xxxxxxxxxxxx>]

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.

In the /var/log/condor/StarterLog.slot1_1 I found messages like:

07/29/25 09:55:49 (pid:400) Job has WantIOProxy=true

07/29/25 09:55:49 (pid:400) Chirp config summary: IO true, Updates true, Delayed updates true.

07/29/25 09:55:49 (pid:400) Sock::bind failed: errno = 99 Cannot assign requested address

07/29/25 09:55:49 (pid:400) IOProxy: couldn't bind: Cannot assign requested address

07/29/25 09:55:49 (pid:400) Couldn't initialize IO Proxy.

In the past I faced this same issue in my CI/CD environment, when trying to run a HTCondor instance for some integration tests.

In that moment I found that in the jic_shadow.cpp:3055 file the value of the proxy IP is fixed to 0xac110001 (172.17.0.1) and I implemented a small patch to pass that value through a parameter.

I did not cared too much because in the operational environments I was using the official HTCondor binaries.

The problem is that now I need to configure an environment with a different docker bridge, and the IOProxy server is not working with the same error.

I do not want to use a patched version there if I can avoid it, so my question is:

There is any other way to configure the IOProxy server that I have overlook?

Thanks! 

Andrés Ayala

I pushed my patch to a pull request: https://github.com/htcondor/htcondor/pull/3561 in case it is useful and there is no better way to tune the IOProxy.

 

Any email message from EUMETSAT is sent in good faith but shall neither be binding nor construed as constituting a commitment by EUMETSAT, except where provided for in a written agreement or contract or if explicitly stated in the email. Please note that any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of EUMETSAT. This message and any attachments are intended for the sole use of the addressee(s) and may contain confidential and privileged information. Any unauthorised use, disclosure, dissemination or distribution (in whole or in part) of its contents is not permitted. If you received this message in error, please notify the sender and delete it from your system.