Merge branch 'main' into troubleshooting-on-linux

website/docs/troubleshooting/index.md

@@ -26,3 +26,11 @@ Podman Desktop has a **Troubleshooting** page to help identify and fix most comm
    Expect a reply such as: _Done in (5.00ms)_.
 
 1. Search for errors in the **Logs** section.
+
+#### Additional resources
+
+- [Troubleshooting Podman](troubleshooting/troubleshooting-podman)
+- [Troubleshooting Podman on Windows](troubleshooting/troubleshooting-podman-on-windows)
+- [Troubleshooting Podman on macOS](troubleshooting/troubleshooting-podman-on-macos)
+- [Troubleshooting Podman on Linux](troubleshooting/troubleshooting-podman-on-linux)
+- [Troubleshooting OpenShift Local](troubleshooting/troubleshooting-openshift-local)

website/docs/troubleshooting/troubleshooting-openshift-local.md

@@ -4,6 +4,28 @@ sidebar_position: 100
 
 # Troubleshooting OpenShift Local
 
-- Check which preset is defined. (`crc config get preset`)
-- Check that `crc` binary is available in the user PATH (`/usr/local/bin/crc`)
-- Check that `crc setup --check-only` is running without errors.
+You can find here troubleshooting help for issues specific to OpenShift Local.
+
+1. To verify that your user can run `crc`, verify that the `crc` binary is available in the user PATH (`/usr/local/bin/crc` on macOS and Linux).
+
+2. To verify that the host is ready to run OpenShift Local, in a terminal, run this command and verify the output has no errors:
+
+   ```shell-session
+   $ crc setup --check-only
+   ```
+
+   Sample output:
+
+   ```shell-session
+   INFO Using bundle path <bundle_path>
+   INFO Checking if running as non-root
+   INFO Checking if running inside WSL2
+   INFO Checking if crc-admin-helper executable is cached
+   crc-admin-helper executable is not cached
+   ```
+
+3. To verify the configured preset, in a terminal, run:
+
+   ```shell-session
+   $ crc config get preset
+   ```