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

It is currently not possible to expose or modify the Docker client connection pool size in Portainer via environment variables or configuration files without recompiling the binary. The value is hard-coded within the Go client implementation used by the application.

Technical Context and Constraints

Portainer utilizes a Go-based Docker client that defaults to a fixed pool of 10 idle connections per endpoint. Because this is a compiled constant rather than a variable mapped to a configuration provider, there is no runtime mechanism to override it. This limitation can lead to intermittent connection exhaustion during high-concurrency events, such as bulk stack deployments or automated CI/CD pipeline triggers.

Safe Limits and File Descriptors

If you choose to rebuild the binary with a higher limit, the primary constraint is the host's file descriptor (FD) capacity. Each connection in the pool consumes a file descriptor. To avoid system-wide instability or Portainer crashes, follow these guidelines:

• Calculation: Total pooled connections = (Pool Size) × (Number of Managed Endpoints).
• Safety Margin: Ensure the total pooled connections do not exceed 50% of the ulimit -n (open files limit) assigned to the Portainer process.
• Verification: Check your current limits using the following command on the host:

  ulimit -n

Edition Availability and Roadmap

There is currently no documented evidence that Portainer Business Edition provides a configurable pool size setting. Based on available technical specifications, both the Community and Business editions share the same underlying Docker client connection logic. There is no publicly available roadmap entry confirming a transition to a tunable runtime variable for this specific setting.

Recommended Mitigation Steps

1. Reduce Concurrency: Throttle CI/CD pipelines to avoid simultaneous bulk API calls to a single endpoint.
2. Monitor FD Usage: Track the number of open files for the Portainer process to determine if you are hitting system limits before attempting a custom build.
3. Host Tuning: Increase the nofile limit in /etc/security/limits.conf for the user running Portainer to provide more headroom.

Diagnostic Detail Needed: To provide a more specific recommendation on FD limits, please provide the total number of Docker endpoints currently managed by your Portainer instance.