[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Hi Gregg,

I was checking and looks like docker creates always the docker0 bridge in all the systems with a default configuration.
In the systems with a custom default network however is called differently, so I still need to be able to choose the network name.

Regards,
Andrés


De: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> en nombre de Greg Thain via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Enviado: miércoles, 30 de julio de 2025 00:20
Para: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Cc: Greg Thain <gthain@xxxxxxxxxxx>
Asunto: Re: [HTCondor-users] IOProxy server for docker jobs not using the default bridge network
 
WARNING: This email originated outside the organisation. Treat links and attachments with caution.

On 7/29/25 05:18, Andres Ayala wrote:
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



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.