FR: Automated systemd service creation

[UebelAndre]

One of the things that I find unnecessarily cumbersome about the lack of a daemon from podman is that users have to create services for each pod themselves. Would it be possible/sensible to add a helper command to podman-compose for installing a service that runs as the user who executed the command? This would solve for situations where users generate service files differently for each use case leading to inconsistent behavior and various unintentional bugs. An automated way to setup a service to restart a pod and it's containers on a reboot would greatly help.

[rhatdan]

I actually think this should be fixed in Podman, basically drop a unit file that runs only one time at boot, With something like podman start --restart that searches through all of the containers that have restart enabled, and then start them.

@mheon WDYT?

[mheon]

I might do a podman system command here that wraps around podman start instead (I dislike adding really-specific options to common commands) but the general approach is a thumbs-up from me.

[UebelAndre]

Any estimates for a timeline for this? I'm not super up to date with the on-goings of podman-compose 😅

[rhatdan]

This would be done in a different project, and then podman-compose could take advantage.

@mheon podman system boot or something similar would be fine with me.

[UebelAndre]

@rhatdan Is there an issue or PR in that other project I could track?

[rhatdan]

It would be best to open an issue in Podman and then monitor it from there.

[UebelAndre]

I created https://github.com/containers/podman/issues/8779

It was unclear to me that I needed to do this given the conversation earlier in this ticket. I'll keep this ticket open until either this feature is implemented or the upstream issue is done in such a way that this request is no longer needed.