mirror of
https://github.com/containers/podman.git
synced 2025-05-17 15:18:43 +08:00
quadlet: document cgroupv2 requirement
Units created with quadlet need cgroupv2 in order to work. Fixes #19365 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This commit is contained in:
@ -59,6 +59,8 @@ Adding the following snippet to a Quadlet file extends the systemd timeout to 15
|
||||
TimeoutStartSec=900
|
||||
```
|
||||
|
||||
Quadlet requires the use of cgroup v2, use `podman info --format {{.Host.CgroupsVersion}}` to check on the system.
|
||||
|
||||
### Service Type
|
||||
|
||||
By default, the `Type` field of the `Service` section of the Quadlet file does not need to be set.
|
||||
|
@ -76,7 +76,7 @@ stateDiagram-v2
|
||||
s2 --> container: socket inherited via exec
|
||||
```
|
||||
|
||||
This type of socket activation can be used in systemd services that are generated from container unit files (see [podman-systemd.unit(5)](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html)) or from the command [`podman generate systemd`](https://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html).
|
||||
This type of socket activation can be used in systemd services that are generated from container unit files (see [podman-systemd.unit(5)](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html)) (Note, quadlet requires the use of cgroup v2) or from the command [`podman generate systemd`](https://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html).
|
||||
The container must also support socket activation. Not all software daemons support socket activation
|
||||
but it's getting more popular. For instance Apache HTTP server, MariaDB, DBUS, PipeWire, Gunicorn, CUPS
|
||||
all have socket activation support.
|
||||
|
Reference in New Issue
Block a user