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.

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

docs: update the troubleshooting guide #3091

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
284 changes: 0 additions & 284 deletions website/docs/troubleshooting.md

This file was deleted.

28 changes: 28 additions & 0 deletions website/docs/troubleshooting/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
sidebar_position: 7
---

# Troubleshooting

If you cannot find your issue here or in the documentation, please fill an issue on our [repository](https://github.com/containers/podman-desktop/issues). You can also explore the [discussions](https://github.com/containers/podman-desktop/discussions) and do a search on similar issues on the [repository](https://github.com/containers/podman-desktop/issues).

## Using the **Troubleshooting** page

Podman Desktop has a **Troubleshooting** page to help identify and fix most common errors.

#### Procedure

1. To open the **Troubleshooting** page, click the **<icon icon="fa-solid fa-lightbulb" size="lg" />** icon.
1. To test the connection to the container engine, click the **Ping** button.

Expect a reply such as: _Responded: 79,75 (9.10ms)_.

1. To test Click the **Check containers** button.

Expect a reply such as: _Responded: 16 containers (108.70ms)_.

1. When connection to the container engine failed, to recreate connections to the sockets, click the **Reconnect providers** button.

Expect a reply such as: _Done in (5.00ms)_.

1. Search for errors in the **Logs** section.
11 changes: 11 additions & 0 deletions website/docs/troubleshooting/troubleshooting-on-linux.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
sidebar_position: 30
---

# Troubleshooting on Linux

You can find here troubleshooting help for issues specific to Linux.

## Podman Desktop does not manage native Podman

Podman Desktop manages Podman machines in virtual machines, and does not handle native Podman installation configuration files.
53 changes: 53 additions & 0 deletions website/docs/troubleshooting/troubleshooting-on-macos.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
sidebar_position: 20
---

# Troubleshooting on macOS

You can find here troubleshooting help for issues specific to macOS.

### Podman machine on Apple Silicon

#### Issue

If you are using an Apple Silicon and brew, you might encounter the following error when starting Podman from Podman Desktop:

```shell-session
Error: qemu exited unexpectedly with exit code 1, stderr: qemu-system-x86_64: invalid accelerator hvf
qemu-system-x86_64: falling back to tcg
qemu-system-x86_64: unable to find CPU model 'host'
```

#### Explanation

Podman machine is running as a `x86_64` process and it could be due to a dual install of homebrew: one for `x86_64` and one for `arm64`.

#### Solution

1. Uninstall your `x86_64` Podman machine by using one of these methods:

- Uninstall Podman machine on your `x86_64` brew install, from a terminal running under rosetta:

```shell-session
$ brew uninstall podman-machine
```

- Uninstall brew `x86_64` as most brew recipe have now arm64 support. Follow [these instructions](https://github.com/homebrew/install#uninstall-homebrew) from a terminal running under rosetta.

1. Run a terminal in native mode (default) and install Podman machine

```shell-session
$ brew install podman-machine
```

1. Delete your Podman machine virtual machines.

```shell-session
$ podman machine rm podman-machine-default
```

1. Create a Podman machine:

```shell-session
$ podman machine init
```
Loading
Loading