Skip to content
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

Support for Podman unit files (Quadlet) #2861

Closed
pvdspoel22 opened this issue Feb 14, 2024 · 2 comments
Closed

Support for Podman unit files (Quadlet) #2861

pvdspoel22 opened this issue Feb 14, 2024 · 2 comments
Labels
feature-request New feature or request

Comments

@pvdspoel22
Copy link

pvdspoel22 commented Feb 14, 2024

Hi,

Quoting from the podman-systemd man pages, as they explain best.. ;-)

SYNOPSIS

   name.container, name.volume, name.network, *.kube

Podman unit search path:

          • /etc/containers/systemd/
          • /usr/share/containers/systemd/

Podman user unit search path:

          • $XDG_CONFIG_HOME/containers/systemd/ or ~/.config/containers/systemd/
          • /etc/containers/systemd/users/$(UID)
          • /etc/containers/systemd/users/

DESCRIPTION

   Podman  supports  starting containers (and creating volumes) via systemd by using a systemd generator.  These files are read during boot (and when
   systemctl daemon-reload is run) and generate corresponding regular systemd service unit files. Both system and user systemd units are supported.

   The Podman generator reads the search paths above and reads files with the extensions .container .volume and *.kube, and for each file generates a
   similarly named .service file. 

   Files with the .network extension are only read if they are mentioned in a .container file. See the Network= key.

   The  Podman  files use the same format as regular systemd unit files.  Each file type has a custom section (for example, [Container]) that is han‐
   dled by Podman, and all other sections are passed on untouched, allowing the use of any normal systemd configuration options like dependencies  or
   cgroup limits.
@pvdspoel22 pvdspoel22 added the feature-request New feature or request label Feb 14, 2024
@keith-hall
Copy link
Collaborator

I believe this may have been added in #2866

@pvdspoel22
Copy link
Author

Thanks @keith-hall , this indeed covers what I was requesting. Excellent!
Looking forward to testing this. I'll close this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants