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

Issue
The Logs tab for a container is empty or does not show any new logs.
Solution
  1. Verify container state: Ensure that the container you are examining is currently in a Running state.
  2. Verify application output: Confirm the application inside the container sends its logs to the console (stdout/stderr) for Podman to display.
  3. Check Podman machine: Ensure the underlying Podman machine is running and connected. Go to Settings > Resources, and verify the status of the machine.
Issue
The Podman machine is not running, which prevents access to container logs.
Solution

Viewing container logs requires an active Podman Machine.

  1. Go to Settings > Resources in the navigation pane.
  2. Locate your Podman machine, such as podman-machine-default.
  3. If the status is Stopped, click the Start icon to launch the machine.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top