3 ms·
IIRC this was causing some exotic problems when deploying docker images based on musl.
by develatio 3y ago
IIRC this was causing some exotic problems when deploying docker images based on musl.
- tyingq 3y agoI think there's also still some potential problems because it still does some things differently than glibc. Musl defaults to parallel requests if you define more than one nameserver (multiple --dns=, for example, for the docker daemon)...where glibc uses them in the order you provide them. To be clear, that's not "wrong", but just different maybe from what docker was expecting.
- LaLaLand122 3y agoI really hope it does some things differently than glibc: https://sourceware.org/bugzilla/show_bug.cgi?id=19643 https://sourceware.org/bugzilla/show_bug.cgi?id=19643 In any case glibc uses NSS, so what glibc does depends on the configuration. It may well just forward the request to systemd-resolved.