Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#68633 - [podman-compose] add systemd service

Attached to Project: Community Packages
Opened by tinywrkb (tinywrkb) - Sunday, 15 November 2020, 15:14 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 16 November 2020, 17:20 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To David Runge (dvzrv)
Filipe LaĆ­ns (FFY00)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

This adds an initial systemd system service. The changes are against the pkgver bump in issue #68632.

By default, the compose filename is podman-compose.yml as I believe other users like myself who switched away from docker are not looking back and we're running podman not docker.
A conf.d file was added for those who want to set back the compose filename as docker-compose.yml.
Those users will also need to symlink /etc/podman to /etc/docker.

This is not perfect, the running services will appear as thawing, though also might not if started after boot.

A systemd user service was not added as I'm not running rootless containers and can't test it.
This task depends upon

Comment by tinywrkb (tinywrkb) - Sunday, 13 June 2021, 17:18 GMT
** edit: You can ignore the rest of the post below. My updated systemd service files can be found in the following link: https://github.com/tinywrkb/pkgbuilds/tree/main/podman-compose-fixed **


I'm attaching a link to a commit adding a working systemd user service file.
Only tested with an updated git build, at this point I don't really care about the terribly outdated stable release which is missing support for volumes, annotations (crun's keep_original_groups), and bug fixes.
Note the setting of xdg dirs, without these, Podman will try creating its folders, or at least its storage root dir, directly under the user's home. **edit: it's not need, the source of the issue was in my configs.**
Like the systemd system service, the defaults can be overridden by a conf.d.
You should be aware that the latest development code prefers a `compose.yaml` and `compose.yml` compose file instead of `docker-compose.yaml`, I probably gonna update later my systemd service file accordingly.

https://github.com/tinywrkb/pkgbuilds/commit/c3a8d29c9b03e84181046b54a01a297fdea8fe5b#diff-9d1096439a4eed15f59c834bcb93b34daeaff9133475e27c268cd9ee7db5406f
Comment by David Runge (dvzrv) - Friday, 06 May 2022, 18:28 GMT
@tinywrkb: Have you tried to upstream this addition?

It is always best to try and streamline this for all downstreams (read: distributions), which is benificial for users.
Comment by tinywrkb (tinywrkb) - Friday, 06 May 2022, 18:55 GMT
@dvzrv podman-compose's developer is implementing generation of service during run-time. Hopefully, it will have the option to set root filesystem target, so we could run this during package().

https://github.com/containers/podman-compose/issues/307

Loading...