docs: using the Troubleshooting page (#3083)

Signed-off-by: Fabrice Flore-Thébault <ffloreth@redhat.com>
This commit is contained in:
Fabrice Flore-Thébault 2023-07-03 11:54:48 +02:00 committed by GitHub
parent 71736141c5
commit 5b3ed5db45
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -6,6 +6,27 @@ sidebar_position: 7
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.
## Podman Issues
### Unable to see any image or container after downloading Podman Desktop