mirror of
https://github.com/containers/podman.git
synced 2025-08-06 11:32:07 +08:00
APIv2 add generate systemd endpoint
Add support for generating systemd units via the api and podman-remote. Change the GenerateSystemdReport type to return the units as map[string]string with the unit name as key. Add `--format` flag to `podman generate systemd` to allow the output to be formatted as json. Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
This commit is contained in:
@ -10,7 +10,7 @@ podman\-generate\-systemd - Generate systemd unit file(s) for a container or pod
|
||||
**podman generate systemd** will create a systemd unit file that can be used to control a container or pod.
|
||||
By default, the command will print the content of the unit files to stdout.
|
||||
|
||||
Note that this command is not supported for the remote client.
|
||||
_Note: If you use this command with the remote client, you would still have to place the generated units on the remote system._
|
||||
|
||||
## OPTIONS:
|
||||
|
||||
@ -20,6 +20,10 @@ Generate files instead of printing to stdout. The generated files are named {co
|
||||
|
||||
Note: On a system with SELinux enabled, the generated files will inherit contexts from the current working directory. Depending on the SELinux setup, changes to the generated files using `restorecon`, `chcon`, or `semanage` may be required to allow systemd to access these files. Alternatively, use the `-Z` option when running `mv` or `cp`.
|
||||
|
||||
**--format**=*format*
|
||||
|
||||
Print the created units in specified format (json). If `--files` is specified the paths to the created files will be printed instead of the unit content.
|
||||
|
||||
**--name**, **-n**
|
||||
|
||||
Use the name of the container for the start, stop, and description in the unit file
|
||||
|
Reference in New Issue
Block a user