Repository navigation
[FEAT] Add possibility to change timeout from env variables or something #45
Description
Is this a new feature request?
- I have searched the existing issues
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
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
github-actions commentedon Jun 4, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
LinuxServer-CI commentedon Jul 5, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
dbrodie commentedon Jul 13, 2026
This is actually very useful for making promtail connect over the docker socket proxy easier, and disconnect / reconnect less.
LinuxServer-CI commentedon Aug 14, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Salvora commentedon Oct 3, 2026
Same here
A third client type: BuildKit image builds through the proxy (buildx with the daemon's builder, which uses the /session endpoint).
That connection carries nothing while a long RUN step is executing, so a build whose step takes longer than the hard-coded 10 minutes is cut with the usual "Response ended prematurely", and the same would hit docker wait, docker logs -f or any other long idle stream. Mounting a modified haproxy.cfg over /templates/ works but means carrying a copy of the whole file across image updates.
Two variables,
TIMEOUT_CLIENT
TIMEOUT_SERVER
defaulting to the current 10m, would cover all of the cases.
thespad commentedon Oct 5, 2026
I'll try and find a clean way to do this.