OS-7754: Ubuntu 18.04 in lx needs different resolver configuration


Issue Type:Improvement
Priority:4 - Normal
Created at:2019-04-18T12:32:45.690Z
Updated at:2021-03-03T22:04:44.341Z


Created by:Former user
Reported by:Former user
Assigned to:Dan McDonald


Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2021-03-03T22:04:44.333Z)

Fix Versions

2021-03-11 modestly priced receptacle (Release Date: 2021-03-11)

Related Links




As reported at https://github.com/joyent/sdc-docker/issues/136, Ubuntu 18.04 configures DNS differently. OmniOS has a fix that hints at how this could be fixed in SmartOS.



Comment by Former user
Created at 2019-07-24T19:40:19.141Z
Updated at 2019-07-24T19:40:45.888Z

@accountid:6248927d45ece00069cb9db5 Any progress on this? IQVIA was asking about this.

Comment by Dan McDonald
Created at 2020-11-30T19:39:46.560Z

Initial testing of placing a new Ubuntu 20 image shows that resolv.conf is being configured by the improved brand scripts at zone boot time.

Comment by Dan McDonald
Created at 2020-11-30T20:25:03.125Z

Testing of Ubuntu 18 image shows DNS gets configured via resolv.conf with the improved brand scripts as well.

Comment by Dan McDonald
Created at 2020-11-30T20:29:57.677Z

NOTE:  Docker images have not yet been tested with this fix, the above results are from normal LX zones.

Comment by Michael Zeller
Created at 2021-03-01T18:47:03.782Z

Just gave this a test on the test Triton in packet.
The old 16.04 image and new wip 20.04 image both pick up DNS settings.

Wiping out resolv.conf and rebooting the zone results in dns settings being populated again from zonecfg.

Comment by Jira Bot
Created at 2021-03-02T23:05:48.907Z

illumos-joyent commit 6e328f367d9cab0f5edb03286642f5533dc2c362 (branch master, by Dan McDonald)

OS-7754 Ubuntu 18.04 in lx needs different resolver configuration

Co-authored-by: Michael Zeller <mike@mikezeller.net>
Reviewed by: Dan McDonald <danmcd@joyent.com>
Reviewed by: Mike Zeller <mike.zeller@joyent.com>
Approved by: Brian Bennett <brian.bennett@joyent.com>