Bug#881310: systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf
Alex King
alex at king.net.nz
Sat Nov 11 23:33:10 GMT 2017
On 12/11/17 00:53, Michael Biebl wrote:
> Hi Alex
>
> Am 11.11.2017 um 00:33 schrieb Alex King:
>> looks like everything that should be in /lib/systemd and
>> /usr/lib/systemd is duplicated in both places?! I guess that is most
>> likely a sysadmin typo, although the system was reloaded relatively
>> recently and I have no idea how this could have happened.
> That sounds like you might have usrmerge enabled, i.e. /lib is a symlink
> to /usr/lib etc. This would explain the resolv.conf in both locations.
>
> Can you post the output of "ls -la /"
>
> Such a system can be created by using debootstrap's --merged-usr or
> installing the usrmerge package in the final system.
>
> Michael
>
Indeed you are correct, this is has a merged /usr:
$ ls -la /
total 68
drwxr-xr-x 18 root root 4096 Nov 11 20:21 .
drwxr-xr-x 18 root root 4096 Nov 11 20:21 ..
lrwxrwxrwx 1 root root 7 Jun 23 23:52 bin -> usr/bin
drwxr-xr-x 2 root root 4096 Apr 4 2017 boot
drwxr-xr-x 12 root root 3380 Nov 9 22:01 dev
drwxr-xr-x 85 root root 4096 Nov 9 23:38 etc
drwxr-xr-x 5 root root 4096 Nov 9 22:59 home
lrwxrwxrwx 1 root root 7 Jun 23 23:52 lib -> usr/lib
lrwxrwxrwx 1 root root 9 Jun 23 23:52 lib32 -> usr/lib32
lrwxrwxrwx 1 root root 9 Jun 23 23:52 lib64 -> usr/lib64
lrwxrwxrwx 1 root root 10 Jun 23 23:52 libx32 -> usr/libx32
drwx------ 2 root root 16384 Jun 23 23:44 lost+found
drwxr-xr-x 2 root root 4096 Jun 23 23:52 media
drwxr-xr-x 2 root root 4096 Jun 23 23:52 mnt
drwxr-xr-x 2 root root 4096 Jun 23 23:52 opt
dr-xr-xr-x 152 root root 0 Nov 9 22:01 proc
drwx------ 6 root root 4096 Nov 11 20:25 root
drwxr-xr-x 18 root root 580 Nov 11 20:35 run
lrwxrwxrwx 1 root root 8 Jun 23 23:52 sbin -> usr/sbin
drwxr-xr-x 2 root root 4096 Jun 23 23:52 srv
dr-xr-xr-x 13 root root 0 Nov 10 23:47 sys
drwxrwxrwt 10 root root 4096 Nov 11 20:35 tmp
drwxr-xr-x 13 root root 4096 Jun 23 23:52 usr
drwxr-xr-x 12 root root 4096 Jun 30 00:56 var
It looks like the VPS was supplied like that.
So it seems like this will be a problem for stretch systems with
usrmerge enabled, and are not using systemd-resolved
Thanks,
Alex
More information about the Pkg-systemd-maintainers
mailing list