containers / containers/podman-compose
Utility processes not restarted if killed
Open
enhancement
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 622
- PR merge metrics
- No merged PRs in 30d
Description
If using the unit file generated with `podman-compose systemd -a create-unit`, systemd doesn't monitor and restart utility processes, such as conmon, slirp4netns, rootlessport or aardvark-dns when they are killed for whatever reason. It would be great to add resilience to the systemd setup. It could, perhaps, be achieved by splitting up the processes into multiple units and enabling them all with a podman-compose command.
Contributor guide
Assessment
This issue has not been assessed yet.