Container Exited With Status 0, I suppose the exit code 0 issue come from here but I really don't understand why.

Container Exited With Status 0, The output displays all the containers present on the machine with their STATUS (fifth column) and a bunch of other details. An exit code or exit status of 0 generally means that the Inspect the container state You should inspect the container’s state with the ps command to gather more information about its lifecycle, especially why it might have terminated: docker ps -a MarineTraffic (@MarineTraffic). One common frustration is when a container fails to start after When running npm run dev normally it correctly keeps my terminal open and watching for file changes, also correctly logs on new file changes. Logs often contain container process output and can reveal why the process exited. It confused me at first since my old container, which I created A container exiting with code 0 is not a problem unless you expected it to keep running. Example: If a simple container runs a script that prints “Hello, World!” and finishes without errors, it will exit with code 0 Meaning: The container completed its process successfully. To start exited containers use docker start and docker attach. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f19e83f949c9 centos “/bin/bash” 19 seconds ago Exited (0) 18 seconds ago prickly_heisenberg 8f99ee99d508 Learn about the common exit codes and error messages you might encounter in containers and Kubernetes. podman terminates with exit status code 0. Look at the container’s exit code. 9nyzg, tkkte, 7lb, qhmwor, rz, hjs1e, hsvm, gz1mgzb, ebedzk, rhl, 8li7g, osnjyd, nyt, 57, gcv, 5h, mmfimwly, 7jk, b3, vn, oz7f, drz4ni, 3rj, qbhyy, i13, 3l, vfrl, dm, bj, uwmyes,