I prepared a qemu-x86-64 disk image that can reproduce this symptom at
https://drive.google.com/drive/folders/1ObSUu3DCF2r4tzcGrykhBCRpPSemHNiu
After logging in as root with password root,
systemd-nspawn -M container1 -n -b
reproduces the symptom, that is,
/bin/systemd-sysusers talks with
From: Michael Biebl
Date: Sun, 9 Feb 2020 08:53:33 +0100
> Not sure what the right solution is. One might be, that the nis NSS
> module handles this situation (rpcbind.socket running, rpcbind.service
> not running) better, or that rpcbind.socket changes its ordering to
> avoid this situation.
>
Am 09.02.20 um 02:24 schrieb Ryutaroh Matsumoto:
> Control: tags -1 + fixed - moreinfo
> Control: retitle -1 Fix found: systemd-sysusers hangs if nis is
> enabled in a systemd-nspawn container
>
> I found a solution (or a workaround).
>
> The problem is that
> (1) systemd-sysusers tries to use
Control: tags -1 + fixed - moreinfo
Control: retitle -1 Fix found: systemd-sysusers hangs if nis is
enabled in a systemd-nspawn container
I found a solution (or a workaround).
The problem is that
(1) systemd-sysusers tries to use Sun RPC (TCP connection to 127.0.0.1:111)
in a nis enabled
Am 07.02.20 um 08:14 schrieb Ryutaroh Matsumoto:
>> Do you have nscd installed inside the container (looking at the strace
>> it appears you might have not).
>
> I installed "unscd" instead of "nscd", as "unscd" is said to be less buggy.
>
>> Is nscd installed outside of the container where you
> Do you have nscd installed inside the container (looking at the strace
> it appears you might have not).
I installed "unscd" instead of "nscd", as "unscd" is said to be less buggy.
> Is nscd installed outside of the container where you don't see the problem?
The host running container also
The container is started as
systemd-nspawn -M bullseye --network-macvlan=eno1 -b
The option --network-macvlan=eno1 is necessary so that the container
can talk with the NIS server running on a third computer (not a container
nor the host running the container).
Ryutaroh
From: Ryutaroh Matsumoto
Do you have nscd installed inside the container (looking at the strace
it appears you might have not).
Does it help if you install nscd?
Is nscd installed outside of the container where you don't see the problem?
signature.asc
Description: OpenPGP digital signature
Hi Michael,
Thank you for paying attention to this.
> Do you have users/groups defined in
> /usr/lib/sysusers.d/ or /etc/sysusers.d which are only resolvable via NIS?
The above directories are untouched. The container was made by
mmdebstrap --variant=debootstrap bullseye.
/etc/passwd nor
Control: tags -1 + moreinfo
Hi!
Am 07.02.20 um 02:55 schrieb Ryutaroh Matsumoto:
> * the above hang-up does not happen if "nis" is removed from
> /etc/nsswitch.conf
> * the above hang-up is NOT observed outside a container.
> * I have no idea if it is an upstream issue.
> * Both host and
One more question:
Do you have users/groups defined in
/usr/lib/sysusers.d/ or /etc/sysusers.d which are only resolvable via NIS?
signature.asc
Description: OpenPGP digital signature
11 matches
Mail list logo
