From: Piviul <piviul@riminilug.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] systemd-logind.service
Date: Thu, 8 Sep 2022 11:58:51 +0200 [thread overview]
Message-ID: <b520b36f-a052-4356-285e-334bc3945a71@riminilug.it> (raw)
In-Reply-To: <CAPzRAJbjnr5RhX1_R17hnPx+2sRf39rOi3kQ7SMyBtpMtc8-eg@mail.gmail.com>
On 05/09/22 12:27, Kalpesh Sejpal wrote:
> Hi,
>
> It's better to enable features Flag nesting=1 for each LXC container with
> that error.
>
> Please, check security conserns before changing it.
>
> If you can't do that then another alternative it to mask systemd-logind
> service.
Hi Kalpesh, thank you very much. In effect both solution seems to work.
There are security risk to set nesting flag on unprivileged container?
Piviul
next prev parent reply other threads:[~2022-09-08 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:27 Kalpesh Sejpal
2022-09-08 9:58 ` Piviul [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-02 8:26 Piviul
2022-09-02 7:23 Piviul
[not found] ` <mailman.49.1662383601.354.pve-user@lists.proxmox.com>
2022-09-07 4:33 ` Piviul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b520b36f-a052-4356-285e-334bc3945a71@riminilug.it \
--to=piviul@riminilug.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox