From ee0ba1e0dc01a2f8a24b00d4c86821cd4adbadcc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabrice=20Flore-Th=C3=A9bault?= Date: Wed, 23 Aug 2023 13:36:52 +0200 Subject: [PATCH] docs: added _Recovering from a failed start_ to troubleshooting (#3579) Co-authored-by: Charlie Drage --- .../troubleshooting-podman-on-macos.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/website/docs/troubleshooting/troubleshooting-podman-on-macos.md b/website/docs/troubleshooting/troubleshooting-podman-on-macos.md index 58213899e9e..b47d4454fcd 100644 --- a/website/docs/troubleshooting/troubleshooting-podman-on-macos.md +++ b/website/docs/troubleshooting/troubleshooting-podman-on-macos.md @@ -99,3 +99,21 @@ $ podman machine init ``` You should be a happy camper from here. + +## Recovering from a failed start + +After a failed start, the Podman machine might be unable to start because a QEMU process is still running and the PID file is in use. + +#### Workaround + +1. Kill the remaining QEMU process and stop the Podman machine: + + ```shell-session + $ ps -edf | grep qemu-system | grep -v grep | awk '{print $2}' | xargs -I{} kill -9 {}; podman machine stop + ``` + +2. Start the Podman machine. + +#### Solution + +Use Podman 4.6.1 or greater.