[OE-core] volatile-binds and DNS

[Kristian Amlie]

On 18/05/17 14:30, Andrea Galbusera wrote:
> On Thu, May 18, 2017 at 9:16 AM, Kristian Amlie
> <kristian.amlie at mender.io <mailto:kristian.amlie at mender.io>> wrote:
> 
>     We've discovered that one of the recent commits to poky has broken DNS
>     resolution in our image. The commit in questions is this one:
> 
>     -------------------
>     commit fcd48092d7bcab0cad2606e65332da62420935ad
>     Author: Joe Slater <jslater at windriver.com
>     <mailto:jslater at windriver.com>>
>     Date:   Fri Mar 31 03:06:33 2017
> 
>         volatile-binds: correct some errors reported by systemd
> 
>         systemd-tmpfiles-setup will fail at boot, so we suppress
>         the default versions of etc.conf and home.conf.
> 
>         We also make sure that /var/{cache,spool} and /srv are writeable
>         if they exist.
>     ...
>     -------------------
> 
>     The problem is that this suppresses the creation of a /etc/resolv.conf
>     file, and without that DNS does not work.
> 
>     The file is a symlink to the resolv.conf that systemd provides in
>     /run/systemd/resolve/resolv.conf, so it could potentially be
>     prepopulated, but I admit I don't fully understand how this fits
>     together.
> 
>     Any advice?
> 
> 
> There's a bug open on this [1]. My workaround as for now is to apply
> [2], but I'm not completely aware of the issue that suggested the
> original commit you mention, hence there might be a better approach to
> fix this...
> 
> [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11331
> [2] http://lists.openembedded.org/pipermail/openembedded-core/2017-April/136074.html

Thanks. Yes, that looks like the same issue. Reverting the line seems to
work, but this should ideally work out of the box. Unfortunately I don't
know enough about volatile-binds to suggest a proper fix...

-- 
Kristian