Podman stopped working after too many connections was opened (All pipe instances are busy) #23392
Labels
kind/bug
Categorizes issue or PR as related to a bug.
machine
remote
Problem is in podman-remote
stale-issue
windows
issue/bug on Windows
Issue Description
We have several components with unit tests which needs a (Kafka) container for execution. When we execute the unit tests for the components sequentially, every thing is fine. But when we execute the unit tests for the different components parallel, the tests stop working after some time and from that point on all remaining tests gets a timeout when they try to connect to the container. Afterwards it is possible to stop the container and start a new one, but also to the new container the connection is no more possible (timeout). After a restart of podman machine following error occurs:
Another colleague who is using docker is able to execute the tests.
Steps to reproduce the issue
Steps to reproduce the issue:
Describe the results you received
See issue description
Describe the results you expected
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Windows 11
wsl --version:
WSL-Version: 2.0.14.0
Kernelversion: 5.15.133.1-1
WSLg-Version: 1.0.59
MSRDC-Version: 1.2.4677
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows-Version: 10.0.22631.3737
Additional information
No response
The text was updated successfully, but these errors were encountered: