Score:0

Systematic way to troubleshoot systemd settings in unprivileged LXC

fr flag

Every now and then I fail to get unprivileged LXC containers running. For some of them I find knowledge from others e.g., which sandboxing options should be disabled to make it work. This time with freeradius, I don't.

freeradius runs nicely in an unprivileged container, if I start it manually, without the sandboxing of systemd. However, I'd like to stay close to the Debian default setting.

Setting systemctl log-level debug I can see that it fails to perform some mounts, which is clear in an unprivileged container. But I have no idea, why systemd would do such mounts in the first place i.e., which option causes systemd to perform the failing steps.

Is there any systematic way to trace what systemd is doing and how the configuration should be adapted?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.