Ubuntu
network-manager package

  1. Bug #1647031
  2. Comment #36

Comment 36 for bug 1647031

Revision history for this message
Blaisorblade (p-giarrusso) wrote :

Replying to #35:
> So, I'm downgrading this from critical to high since it only hits users of 16.10 server in a few corner cases (i.e. containers, chroots without libnss-resolve installed). It should still be SRUed.

Another corner case seems to be binaries linked against musl libc, since they do not use NSS.

We're getting many reports related the problem on the Haskell stack tool (https://github.com/commercialhaskell/stack/issues/2536#issuecomment-285327722), and we indeed link against musl libc (https://github.com/commercialhaskell/stack/issues/3060).

To be sure, is the plan to make the local DNS proxy at least resolve CNAME correctly on Yakkety and future releases, either by fixing systemd or switching to dnsmasq? Only providing `libnss-resolve` is not enough. I'm not aware of us needing fancier DNS features, but correct CNAME support would be great.

I understand you don't include musl libc, but except for this bug it's an attractive option for shipping one universal Linux binary, which I suggest Ubuntu should keep supporting. Since the bug affects other scenarios anyway, I think it's reasonable to hope for a fix. I appreciate your effort.