Chapter 2. Troubleshoot container issues
Troubleshoot issues encountered when viewing container logs in Red Hat build of Podman Desktop. The primary focus is on resolving instances where the log stream is empty or inactive.
2.1. Fix empty or missing container logs Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
- Issue
- The Logs tab for a container is empty or does not show any new logs.
- Solution
- Verify container state: Ensure that the container you are examining is currently in a Running state.
- Verify application output: Confirm the application inside the container sends its logs to the console (stdout/stderr) for Podman to display.
- Check Podman machine: Ensure the underlying Podman machine is running and connected. Go to Settings > Resources, and verify the status of the machine.
2.2. Container logs inaccessible when Podman machine is stopped Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
- Issue
- The Podman machine is not running, which prevents access to container logs.
- Solution
Viewing container logs requires an active Podman Machine.
- Go to Settings > Resources in the navigation pane.
-
Locate your Podman machine, such as
podman-machine-default. - If the status is Stopped, click the Start icon to launch the machine.