Portainer Docker API Connection Pool Size: Need for Runtime Configurable Limit

The goal is to prevent intermittent connection pool exhaustion when Portainer handles many simultaneous Docker API requests, such as bulk stack deployments or CI pipelines.

Currently, the Docker Go client used by Portainer creates a fixed pool of 10 idle connections per endpoint, a value that is hard‑coded and not exposed through the UI, environment variables, or configuration files. Adjusting it requires rebuilding the binary, leaving administrators without a supported runtime option and creating an unresolved decision about whether to make the pool size tunable.

Uncertainty remains around the feasibility of exposing this limit without recompiling, the safe upper bounds given host file‑descriptor limits, and whether any edition already provides a configurable setting.

Is it possible to expose the Docker client connection pool size as an environment variable or configuration option in Portainer without recompiling?
What are the recommended safe limits for the pool size relative to typical host file‑descriptor capacities?
Does Portainer Business edition already offer a configurable pool size, and if not, is there a roadmap to add this feature?