You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently facing an issue with Podman containers exiting immediately after startup on a RHEL 9.6 system (Plow OS). I have installed Podman using pip3, and I am running containers using podman-compose, converted from a working docker-compose.yml.
My application is a customized Node.js service running on Ubuntu base image with Apache2. These containers run continuously without issues using Docker, but under Podman started as a daemon, all containers exit with various codes (0, 137, 143, etc.) after launch without any use
Steps I've followed:
Installed Podman via pip3 install podman.
Converted and configured the Docker Compose setup to work with Podman Compose.
Used the same base image that worked fine in Docker.
Verified that my application works outside the container environment.
Issues Observed:
Containers exit immediately.
Logs do not indicate any application-level crash.
No errors in startup scripts or entrypoints.
Could you please assist in identifying what might be causing this behavior? Also, are there known compatibility issues with Podman running Node.js + Apache2 apps inside Ubuntu images on RHEL 9.6?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Dear Podman Support Team,
I am currently facing an issue with Podman containers exiting immediately after startup on a RHEL 9.6 system (Plow OS). I have installed Podman using pip3, and I am running containers using podman-compose, converted from a working docker-compose.yml.
My application is a customized Node.js service running on Ubuntu base image with Apache2. These containers run continuously without issues using Docker, but under Podman started as a daemon, all containers exit with various codes (0, 137, 143, etc.) after launch without any use
Steps I've followed:
Installed Podman via pip3 install podman.
Converted and configured the Docker Compose setup to work with Podman Compose.
Used the same base image that worked fine in Docker.
Verified that my application works outside the container environment.
Issues Observed:
Containers exit immediately.
Logs do not indicate any application-level crash.
No errors in startup scripts or entrypoints.
Could you please assist in identifying what might be causing this behavior? Also, are there known compatibility issues with Podman running Node.js + Apache2 apps inside Ubuntu images on RHEL 9.6?
Looking forward to your support.
Beta Was this translation helpful? Give feedback.
All reactions