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:
podman machine start
Starting machine "podman-machine-default"
API forwarding for Docker API clients is not available due to the following startup failures.
CreateFile \\.\pipe\docker_engine: All pipe instances are busy.
Podman clients are still able to connect.
Error: machine did not transition into running state: ssh error: ssh: handshake failed: read tcp [::1]:60755->[::1]:65395: wsarecv: An existing connection was forcibly closed by the remote host.
Another colleague who is using docker is able to execute the tests.
Steps to reproduce the issue
Steps to reproduce the issue:
Start a container.
Send multiple request in parallel to this container until they run in timeout. (Unfortunately I cannot tell how many request are send in parallel.)
Restart the podman machine
Describe the results you received
See issue description
Describe the results you expected
I expect that podman can handle multiple request in parallel and not only sequential processing.
I expect that the same tests which are executable with docker are executable with podman.
podman info output
podman version (after the test execution):
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: failed to connect: ssh: handshake failed: read tcp 127.0.0.1:60786->127.0.0.1:65395: wsarecv: An existing connection was forcibly closed by the remote host.
podman version
Client: Podman Engine
Version: 5.1.1
API Version: 5.1.1
Go Version: go1.22.3
Git Commit: bda6eb03dcbcf12a5b7ae004c1240e38dd056d24
Built: Tue Jun 4 23:40:05 2024
OS/Arch: windows/amd64
Server: Podman Engine
Version: 5.1.1
API Version: 5.1.1
Go Version: go1.22.3
Built: Tue Jun 4 02:00:00 2024
OS/Arch: linux/amd64
podman info
host:
arch: amd64
buildahVersion: 1.36.0
cgroupControllers:
- cpuset
- cpu
- cpuacct
- blkio
- memory
- devices
- freezer
- net_cls
- perf_event
- net_prio
- hugetlb
- pids
- rdma
- misc
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: conmon-2.1.10-1.fc40.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.10, commit: '
cpuUtilization:
idlePercent: 99.72
systemPercent: 0.15
userPercent: 0.13
cpus: 16
databaseBackend: sqlite
distribution:
distribution: fedora
variant: container
version: "40"
eventLogger: journald
freeLocks: 2048
hostname: RDDE00B4
idMappings:
gidmap: null
uidmap: null
kernel: 5.15.133.1-microsoft-standard-WSL2
linkmode: dynamic
logDriver: journald
memFree: 15669846016
memTotal: 16351825920
networkBackend: netavark
networkBackendInfo:
backend: netavark
dns:
package: aardvark-dns-1.11.0-1.fc40.x86_64
path: /usr/libexec/podman/aardvark-dns
version: aardvark-dns 1.11.0
package: netavark-1.11.0-1.fc40.x86_64
path: /usr/libexec/podman/netavark
version: netavark 1.11.0
ociRuntime:
name: crun
package: crun-1.15-1.fc40.x86_64
path: /usr/bin/crun
version: |-
crun version 1.15
commit: e6eacaf4034e84185fd8780ac9262bbf57082278
rundir: /run/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
os: linux
pasta:
executable: /usr/bin/pasta
package: passt-0^20240624.g1ee2eca-1.fc40.x86_64
version: |
pasta 0^20240624.g1ee2eca-1.fc40.x86_64
Copyright Red Hat
GNU General Public License, version 2 or later
<https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
remoteSocket:
exists: true
path: /run/podman/podman.sock
rootlessNetworkCmd: pasta
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: false
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: true
slirp4netns:
executable: ""
package: ""
version: ""
swapFree: 4294967296
swapTotal: 4294967296
uptime: 0h 1m 20.00s
variant: ""
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /usr/share/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.imagestore: /usr/lib/containers/storage
overlay.mountopt: nodev,metacopy=on
graphRoot: /var/lib/containers/storage
graphRootAllocated: 1081101176832
graphRootUsed: 1362513920
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Supports shifting: "false"
Supports volatile: "true"
Using metacopy: "true"
imageCopyTmpDir: /var/tmp
imageStore:
number: 2
runRoot: /run/containers/storage
transientStore: false
volumePath: /var/lib/containers/storage/volumes
version:
APIVersion: 5.1.1
Built: 1717459200
BuiltTime: Tue Jun 4 02:00:00 2024
GitCommit: ""
GoVersion: go1.22.3
Os: linux
OsArch: linux/amd64
Version: 5.1.1
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