win-sshproxy.exe fails to start after Windows update disables Event Logs #21426
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
After a recent Windows update, it appears that the Event Logs service was disabled automatically. This caused an issue where
podman machine start
could not successfully execute becausewin-sshproxy.exe
failed to start. Manually re-enabling the Event Logs service resolved the issue. However, I believe Podman should not rely on the Event Logs, or at the very least, should provide clearer and more direct error messaging to help diagnose such issues.Steps to reproduce the issue
Steps to reproduce the issue
podman machine start
.Describe the results you received
The
podman machine start
command fails with an error indicating thatwin-sshproxy.exe
failed to start, but it does not specify that this is due to the Windows Event Logs being disabled.Describe the results you expected
Podman should either not rely on Windows Event Logs to start
win-sshproxy.exe
, or provide a clear error message indicating the dependency and how to resolve the issue if the Event Logs service is disabled.podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
The issue was resolved after manually enabling the Event Logs service in Windows.
The text was updated successfully, but these errors were encountered: