-
Notifications
You must be signed in to change notification settings - Fork 544
Respect XDG_CONFIG_HOME when generating systemd unit #477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Samir Benmendil <me@rmz.io>
Signed-off-by: Samir Benmendil <me@rmz.io>
92ccae5 to
92781e4
Compare
I would love if we add --global option as in the referenced comment.
I would love if we keep the sudo in the help.
I would love if we add --global option as in the referenced comment.
The --global option only makes sense with -a create-unit, I wasn't sure how to introduce it nicely. Happy to take advice on how you'd like this handled.
However, I'm not convinced it should exist at all. podman-compose wants to be rootless, providing an easy way to install the systemd unit to the users home directory only is perfectly fine.
I would love if we keep the sudo in the help.
The point of this MR is to install the user systemd unit in the users home directory where sudo is not needed.
However, I'm not convinced it should exist at all. podman-compose wants to be rootless, providing an easy way to install the systemd unit to the users home directory only is perfectly fine.
a typical valid use case is to install podman-compose rootful and used rootless.
Addresses #307 (comment).
Possibly a better approach would be to let package maintainers install this unit file in /usr/systemd/user, but this would break the "single file" design.