Unable to view containers in cockpit-podman

Solution In Progress - Updated -

Environment

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • podman

Issue

  • podman containers are not visible in cockpit-podman UI

Resolution

  • By default, podman.service is expected to stay active only for 5 seconds after which it exits. Please note that this is an expected behavior from podman service. The service waits for API calls for 5 seconds by default and if there are no active connections made during this period, it is automatically set to inactive and this is how it is designed to work. podman.socket will always be active waiting for connections
  • However, in order to display the containers in cockpit-podman, the service always needs to stay active. One can choose to edit the service file of podman to include --time=0 to achieve this
  • Why is podman service in inactive state ? This article explains the steps for keeping podman.service active throughout. The same steps hold good for both root and rootless users but the service file location differs for rootless users.

Root Cause

  • podman.service needs to stay active in order to view podman related contents in cockpit

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments