ubb:/etc/containers/systemd# /usr/lib/systemd/system-generators/podman-system-generator --dryrun
quadlet-generator[3589233]: Error occurred resolving path "/usr/share/containers/systemd": lstat /usr/share/containers/systemd: no such file or directory
quadlet-generator[3589233]: Loading source unit file /etc/containers/systemd/ubb-roundcube.kube
---ubb-roundcube.service---
[Unit]
Description=RoundCube email client
SourcePath=/etc/containers/systemd/ubb-roundcube.kube
RequiresMountsFor=%t/containers
[X-Kube]
Yaml=/opt/roundcube/roundcube.yaml
[Service]
User=roundcube
WorkingDirectory=/opt/roundcube
Restart=always
KillMode=mixed
Environment=PODMAN_SYSTEMD_UNIT=%n
Type=notify
NotifyAccess=all
SyslogIdentifier=%N
ExecStart=/usr/bin/podman kube play --replace --service-container=true /opt/roundcube/roundcube.yaml
ExecStopPost=/usr/bin/podman kube down /opt/roundcube/roundcube.yaml
[Install]
WantedBy=multi-user.target
Running this service results in the following error messages
Jun 11 16:34:04 ubb systemd[1]: Starting ubb-roundcube.service - RoundCube email client...
░░ Subject: A start job for unit ubb-roundcube.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit ubb-roundcube.service has begun execution.
░░
░░ The job identifier is 187629.
Jun 11 16:34:07 ubb systemd[1]: ubb-roundcube.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit ubb-roundcube.service has entered the 'failed' state with result 'protocol'.
Jun 11 16:34:07 ubb systemd[1]: Failed to start ubb-roundcube.service - RoundCube email client.
░░ Subject: A start job for unit ubb-roundcube.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit ubb-roundcube.service has finished with a failure.
░░
░░ The job identifier is 187629 and the job result is failed.
Commenting out the User=roundcube line however results in the pod successfully running (as root). I can also successfully run the pod by doing sudo -u roundcube podman kube play roundcube.yaml.
Steps to reproduce the issue
Steps to reproduce the issue
Make a quadlet file with User= line specifying a non-root user
Run quadlet via systemctl
Describe the results you received
Container should run as the specified non-root user.
Issue Description
In attempting to get a container running as non-root, I'm using the following quadlet configuration.
Which generates this systemd spec
Running this service results in the following error messages
Commenting out the
User=roundcube
line however results in the pod successfully running (as root). I can also successfully run the pod by doingsudo -u roundcube podman kube play roundcube.yaml
.Steps to reproduce the issue
Steps to reproduce the issue
User=
line specifying a non-root userDescribe the results you received
Container should run as the specified non-root user.
Describe the results you expected
Container does not run successfully
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response