Is this a new feature request?
Wanted change
I am using lscr.io/linuxserver/socket-proxy:latest image on my airflow project.
Some of my tasks are docker operators, and some of them takes some time to compute (more than an hour), and for these, I got a Response ended prematurely error related to timeout settings too low from the haproxy.cfg.
I found the solution here:
apache/airflow#58614
For now, I just downloaded the haproxy.cfg file in the container, increase timeout server value and them, I mount this file in /templates/haproxy.cfg in my docker-compose.yml
Reason for change
I think it could be useful and easier for people to configure timeout parameters from docker environment variables instead of mounting a custom .cfg file.
Proposed code change
No response
Is this a new feature request?
Wanted change
I am using lscr.io/linuxserver/socket-proxy:latest image on my airflow project.
Some of my tasks are docker operators, and some of them takes some time to compute (more than an hour), and for these, I got a
Response ended prematurelyerror related to timeout settings too low from the haproxy.cfg.I found the solution here:
apache/airflow#58614
For now, I just downloaded the haproxy.cfg file in the container, increase
timeout servervalue and them, I mount this file in /templates/haproxy.cfg in my docker-compose.ymlReason for change
I think it could be useful and easier for people to configure timeout parameters from docker environment variables instead of mounting a custom .cfg file.
Proposed code change
No response