From 7741e047dd0018a1cb37d956aa94cf1fd15cce17 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Erik=20Sj=C3=B6lund?= Date: Thu, 20 Nov 2025 21:01:42 +0100 Subject: [PATCH] podman-systemd.unit.5: document /sbin/nologin accounts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add command: sudo systemctl --machine username@ --user list-unit-files Fixes: https://github.com/containers/podman/issues/27544 Co-authored-by: Tom Sweeney Signed-off-by: Erik Sjölund --- docs/source/markdown/podman-systemd.unit.5.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/source/markdown/podman-systemd.unit.5.md b/docs/source/markdown/podman-systemd.unit.5.md index 8d06198ed4..d724fb6537 100644 --- a/docs/source/markdown/podman-systemd.unit.5.md +++ b/docs/source/markdown/podman-systemd.unit.5.md @@ -51,7 +51,8 @@ The Podman generator reads the search paths above and reads files with the exten `.volume`, `.network`, `.build`, `.pod`, `.kube`, and `.artifact`, and for each file generates a similarly named `.service` file. Be aware that existing vendor services (i.e., in `/usr/`) are replaced if they have the same name. The generated unit files can be started and managed with `systemctl` like any other systemd service. `systemctl {--user} list-unit-files` -lists existing unit files on the system. +lists existing unit files on the system. To list unit files of a user who has `/sbin/nologin` as a login shell, +run `sudo systemctl --machine username@ --user list-unit-files`. The Podman files use the same format as [regular systemd unit files](https://www.freedesktop.org/software/systemd/man/systemd.syntax.html). Each file type has a custom section (for example, `[Container]`) that is handled by Podman, and all