Comment 10 for bug 1717995
Revision history for this message
| Walter Garcia-Fontes (walter-garcia) wrote | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Same for me. I really don't understand how /etc/resolv.conf should be managed in Ubuntu 17.04. I have the setup described in comment #7. I tried to have only network-manager manage /etc/resolv.conf, but then I loose name resolution in containers.
I think we should open a new bug report, as this one marked with "Fix released" will never get attention. It may also something worth investigating upstream.