Daniel Preussker

@kepi any update?

@muuki88 Is there any news regarding this? We might be facing a similar issue where we want to provide multi-arch Docker Images

if you use RRDCached, then disable it and it will work again. Alternatively upgrade RRD* to a newer version (1.4.8 did not work but 1.7.x did work. I dont know...

@antpuleo2586 sounds very similar to my PR https://github.com/microsoft/ApplicationInsights-node.js/pull/817

Happy to, just trying to find the culprit here. Right now I'm "solving" it by nuking node_modules after every build and reinstalling things. //Edit: Right so even before config.js is...

If that's the sole reason then why not skip resolved? There's no necessity as networkd will propagate /etc/resolv.conf by itself if I remember right. Right now we employ resolved and...

~~For nss-switch there might be https://www.freedesktop.org/software/systemd/man/nss-resolve.html as option. Untested but I can run a quick portage run and see what happens~~ Turns out `/usr/lib64/libnss_systemd.so.2` already exists, let's test nsswitch's config...

I will submit a PR to the baselayout with the nsswitch changes

I would like to keep this issue open despite the merge as the fundamental issue is still the same. I agree that having nsswitch working with systemd is a step...

Ok opened 3 PRs, One is for keeping the current status-quo regarding /etc/resolv.conf and only deals with nsswitch labelled as partial fix. It does not change the behavior of namespaced...