Skip to content

feature: read the Docker client timeout from DOCKER_CLIENT_TIMEOUT - #716

Open
Amadeus-22 wants to merge 1 commit into
QuantConnect:masterfrom
Amadeus-22:feature-364-docker-client-timeout
Open

Amadeus-22 wants to merge 1 commit into
QuantConnect:masterfrom
Amadeus-22:feature-364-docker-client-timeout

Conversation

@Amadeus-22

@Amadeus-22 Amadeus-22 commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Closes #364

Description

The Docker client the CLI creates uses the SDK's default timeout of 60 seconds, which is too short for some Docker hosts. There was no way to change it.

DockerManager now reads DOCKER_CLIENT_TIMEOUT, the same variable Docker Compose uses for this, and passes it to the client. When it is not set or empty, the SDK default is used as before. A value that is not a positive whole number of seconds raises a clear error instead of being silently ignored.

How Has This Been Tested?

  • New tests in tests/components/docker/test_docker_manager.py: default timeout when the variable is unset or empty, the value passed to the client when set, and an error for invalid values (parametrized).
  • Full suite: 2773 passed, 82 skipped.

🤖 Generated with Claude Code

The Docker SDK's default timeout of 60 seconds is too short for some
Docker hosts. DOCKER_CLIENT_TIMEOUT, the variable Docker Compose reads
for the same purpose, now sets the timeout of the client the CLI
creates. When it is not set, the SDK default is used as before, and a
value that is not a positive whole number of seconds is reported
instead of being silently ignored.

Closes QuantConnect#364

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Not possible to set DOCKER_CLIENT_TIMEOUT via CLI

1 participant