Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: added _Recovering from a failed start_ to troubleshooting #3579

Merged
merged 4 commits into from
Aug 23, 2023
Merged

docs: added _Recovering from a failed start_ to troubleshooting #3579

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7a2e489
docs: added _Recovering from a failed start_ - references #3127
themr0c Aug 17, 2023
9eca238
Update website/docs/troubleshooting/troubleshooting-podman-on-macos.md
themr0c Aug 21, 2023
9e5fec2
Merge branch 'main' into issue-3127
themr0c Aug 21, 2023
193ade3
Merge branch 'main' into issue-3127
themr0c Aug 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions website/docs/troubleshooting/troubleshooting-podman-on-macos.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.