Closed frol closed 8 years ago
Do we know where /etc/nsswitch.conf
usually comes from? It is possible it is just missed from the generated glibc package or builder. I'll check soon to see if this is the case.
It seems to be a base OS layout:
filesystem
package owns the file in Arch Linux
$ yaourt -Qo /etc/nsswitch.conf
/etc/nsswitch.conf is owned by filesystem 2015.09-1
No package is associated with the file in Debian and Ubuntu:
$ dpkg -S /etc/nsswitch.conf
dpkg-query: no path found matching pattern /etc/nsswitch.conf
Wierd, but /etc/nsswitch.conf
is created as a symlink:
/ # ls -la /etc/nsswitch.conf
lrwxrwxrwx 1 root root 35 Feb 12 05:35 /etc/nsswitch.conf -> /home/builder/package/nsswitch.conf
Huh... I'm pretty sure I just did a cp -a
... I'll look at it again in a couple days.
cp -a
will copy a symlink if it is a symlink, but in this case, we want to have just a regular file. Could you please remove -a
flag?
Give the latest unreleased tag a try.
It works!
Missing
/etc/nsswitch.conf
configuration results in that glibc-dependent applications ignore/etc/hosts
contents entirely. See the reproduction here:NOTE:
/mnt/ping
utility was copied from my glibc-based host system.I have added the following fix in
frolvlad/alpine-glibc
long time ago, and it proved to work fine for many people since then: