We are using ansible container on our windows workstation to play our playbooks. If the container runs in interactive mode it stops working after some time with the following error:
time="2024-09-25T10:51:53+02:00" level=error msg="Failed to check if 462119b787080b6a9da9818717bd10baef4616df72d0959ca4920e2f7d74bcda should restart: Post \"http://d/v5.2.0/libpod/containers/462119b787080b6a9da9818717bd10baef4616df72d0959ca4920e2f7d74bcda/shouldrestart\": read tcp 127.0.0.1:55168->127.0.0.1:52716: wsarecv: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat."
Error: Post "http://d/v5.2.0/libpod/containers/462119b787080b6a9da9818717bd10baef4616df72d0959ca4920e2f7d74bcda/wait": read tcp 127.0.0.1:55168->127.0.0.1:52716: wsarecv: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
The container is still running after the error in the windows cmd in the background and is finishing normally at some point.
Steps to reproduce the issue
Steps to reproduce the issue
"podman run" in interactive mode with long running script
Describe the results you received
If the interactive mode has no new input for a while, the command ends with the mentioned error.
Describe the results you expected
The command in windows ends normally when the script was successfully executed in the container.
Issue Description
We are using ansible container on our windows workstation to play our playbooks. If the container runs in interactive mode it stops working after some time with the following error:
The container is still running after the error in the windows cmd in the background and is finishing normally at some point.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
If the interactive mode has no new input for a while, the command ends with the mentioned error.
Describe the results you expected
The command in windows ends normally when the script was successfully executed in the container.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting