-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman doesn't respond (hangs on "DoRequest Method: GET URI: http://d/v4.5.1/libpod/_ping") #19113
Comments
thanks for the report @informeti |
Does the command which hangs timeout eventually or just hang forever? Is the podman system service process running, there was a bug with the systemd socket activation recently: #18862 Inside the VM can you provide the service logs with |
It seems to hang forever. In the case of this report, I waited for about 45 minutes before aborting it.
I'm not sure what to look for. In the WSL machine, the
It seems like this log doesn't contain anything:
Then again, right now the issue isn't occurring (I really cant tell what's triggering it, and the frequency varies from multiple times a day to days without issue). Not sure if I'd see any log entries while Podman isn't responding. |
Do you use the default machine setting, i.e. not |
Ahh, while I'm not sure I understood it correctly, I found logs now. I enter the machine using
But now I did remain in the "nested process namespace", and here, I do get a lot of logs (although the service is still marked as inactive and disabled): Here's the relevant part of the log, i.e. starting a bit before the issue occurred, until the point where I "rebooted" the WSL machine with
PS: You'll notice that a container (ms sql server) is logging out stuff that appears as blob data; indeed there's an encoding issue with it, but I don't think this issue is related, since the unresponsiveness also occurs without starting this container. |
The issue occurred again, this time under slightly different circumstances:
This time, I have no logging: The log file stops on Wednesday the 5th, even though I used Podman yesterday (Thursday the 6th) and today (Friday the 7th). Just like in the previously reported case, the socket seems to be running, the service isn't, and the CLI log remains stuck at:
|
am I misremembering or was there not an issue with 4.5.0, which is why we did 4.5.1 so quickly ? |
A friendly reminder that this issue had no activity for 30 days. |
@informeti , perhaps, it is like this one: #19625 |
Yes, this looks fixed by it. I am closing as it seems to be fixed in systemd. |
Bug description
Every now and then, during seemingly normal usage of Podman, the Podman CLI / Podman Desktop / docker-compose will become unresponsive.
I couldn't find any particular trigger. It also occurs with colleagues who installed Podman using the installer.
Once unresponsive, logging of various commands looks like this:
It seems like the issue exists between Windows and the WSL machine. If I manually enter the WSL machine, I can still interact with podman:
The podman socket seems to be running correctly:
Back on the host side, where Podman is still unresponsive, I can still inspect the machine:
Workaround
If I close Podman Desktop, perform
wsl --shutdown
, and start Podman Desktop again (which automatically starts the WSL machine), the issue is gone for the moment being.Operating system
Windows 10
Installation Method
Scoop (Windows)
Version
1.1.0
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: