Re: Manual start of user@<uid>.service failed with permission denied

Date Prev

Date Next

Thread Prev

Thread Next

Date Index

Thread Index

Subject: Re: Manual start of user@<uid>.service failed with permission denied

From: Christopher Wong <Christopher.Wong@xxxxxxxx>

Date: Fri, 8 Dec 2023 08:52:10 +0000

Accept-language: en-US, sv-SE

Cc: "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>

In-reply-to: <ZXIzN18HKQU3iqrO@gardel-login>

References: <DB4PR02MB93348CE807D102500F3FAEF1FE84A@DB4PR02MB9334.eurprd02.prod.outlook.com> <ZXCYQpNJnrnQYEDl@gardel-login> <DB4PR02MB93342C1B40DCDFD251F097B7FE8BA@DB4PR02MB9334.eurprd02.prod.outlook.com> <ZXIzN18HKQU3iqrO@gardel-login>

Hi Lennart,

I know we are not using the pam_systemd. That is the reason we try to run the steps manually. It was possible to start the user@<UID>.service in systemd v253, but it fails now with v254 or later.

Best regards,

Christopher Wong

From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
Date: Thursday, 7 December 2023 at 22:03
To: Christopher Wong <Christopher.Wong@xxxxxxxx>
Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Manual start of user@<uid>.service failed with permission denied

On Do, 07.12.23 18:29, Christopher Wong (Christopher.Wong@xxxxxxxx) wrote:

> Hi Lennart,
>
> We are doing the steps to start up a rootless docker. If I don’t set XDG_RUNTIME_DIR then I will get the below error:
>
> systemd[1925]: Trying to run as user instance, but $XDG_RUNTIME_DIR
> is not set.

pam_systemd is responsible for setting this env var. Most likely you
are missing that from the PAM stack that is used by this user@.service
instance?

> The 503 is a system user. So, just to try it out, I created a user,
> which got the UID 1001. Using that UID gave me the same result as
> the 503.

It's a bad idea to run user stuff as system user.

Lennart

--
Lennart Poettering, Berlin