SSHAdapter pool_connections too big
See original GitHub issuedocker-compose
has an issue when connecting to a remote daemon over SSH.
docker-py
sets the number of connections to 25 which is a problem since sshd
defines MaxSessions
to 10 by default.
My questions:
- why is the default so high in
docker-py
? - could
docker-py
set it to lower by default for the SSH transport so that it works out of the box with an ssh server with default configuration?
In my tests I had to put the limit (num_pools
argument for ApiClient
) to 9, there must be an off-by-one error somewhere in there…
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
POOLSKIM connector too big for my 1" pool inlet.
Im trying to install the POOLSKIM I ordered but the connectors were too big to fit inside the inlet, the inlet also does...
Read more >Intex Pool 1.25 to 1.5 conversion - YouTube
I'm converting from a 1.25 inch to 1.5-inch Hoses and fittings on an INTEX pool system. I have other plans for this pool...
Read more >How to Fit a Pool Hose - eHow
Step 3. Slide the pool hose over the correctly sized male end of adapter. If you are having trouble sliding the hose with...
Read more >Configure connectors :: IDM 7.2.1 - ForgeRock Backstage
Because IDM produces a full property set for all attributes and all object types in the schema, the resulting configuration can be very...
Read more >SSH adapter response IO exception. Connection timed out
However if i try to connect same host using winscp i could connect. SSH adapter configuration is very simple. pastedImage_0.png. What could be ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that’s due to
DEFAULT_NUM_POOLS
. 25 is fine for everything else.Maybe as a quick fix, we can hard-set the num_pools for the SSH transport to (9/10), then look at making it configurable later.
I wonder – could it be counting the underlying network connection as one, then allowing 9 additional sessions on top (essentially meaning the first sessions counts as two)?