I am encountering three issues with run0:
1. not upstream related but Debian (currently) does not install systemd-run0
pamname
2. the man page is incorrect in stating that everything goes through
systemd-run0 pam stack because if you omit --user= then run0 will not go
through pam (you can verif
Hello community,
I face a strange behavior of my containers running using systemd-nspawn : some
directories initially in the volume are not visible inside the container. It
seems this is always the qame "kind" of directories e.g. maybe they are
reserved for specific use ?
Example:
root@target
On Do, 17.10.24 09:58, Dominick Grift (dominick.gr...@defensec.nl) wrote:
>
> I am encountering three issues with run0:
>
> 1. not upstream related but Debian (currently) does not install
> systemd-run0 pamname
Not sure what "pamname" means? Do you mean the PAM stack configuration
file for run0?
Lennart Poettering writes:
> On Do, 17.10.24 09:58, Dominick Grift (dominick.gr...@defensec.nl) wrote:
>
>>
>> I am encountering three issues with run0:
>>
>> 1. not upstream related but Debian (currently) does not install
>> systemd-run0 pamname
>
> Not sure what "pamname" means? Do you mean the
On Do, 17.10.24 11:48, Joel GUITTET (jguittet.opensou...@witekio.com) wrote:
> systemd-nspawn --quiet --boot --network-bridge=br0 --read-only
> --volatile=yes --notify-ready=yes --settings=override
> --slice=${SLICE} --machine=%i
You are using --volatile=yes. See the man page of what it does, you
