Podman infra container in a pod is stopped before application container

Solution Verified - Updated -

Environment

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

Issue

  • When a podman pod is stopped, the infra container exits before the application container exits. Since infra container is exited, it results in losing network connection prematurely.

Resolution

  • When the podman pods are tried to stop, it stops all the containers in the pod simultaneously, including the infra container
  • Since the infra container manages the network connections, its immediate shutdown results in the container losing network connectivity prematurely
  • This prevents it from handling open transactions and exiting cleanly, forcing to terminate the process manually
  • This has been identified as a bug with podman and the is being tracked in JIRA. Please follow the JIRA for updates from the engineering team.

Root Cause

  • Infra container is responsible for managing network connections with other containers; when this goes down, complete network is down in a pod

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