|
From: | Drew C |
Subject: | Re: [PATCH] environment: container: Do not remount network files as read-only. |
Date: | Sat, 26 Mar 2016 09:59:30 -0700 |
Interesting! Is this on Ubuntu as well?On Sat, Mar 26, 2016 at 12:29 PM, Drew C <address@hidden> wrote:
>
> On Sat, Mar 26, 2016 at 7:06 AM, Thompson, David <address@hidden>
> wrote:
>>
>> On Fri, Mar 18, 2016 at 4:51 PM, Ludovic Courtès <address@hidden> wrote:
>> > "Thompson, David" <address@hidden> skribis:
>> >
>> >> I noticed that 'guix environment --container --network' didn't work on
>> >> an Ubuntu machine I was on, and the culprit was remounting things like
>> >> /etc/resolv.conf read-only after the initial bind mount.
>
>
>
> One thing that I have run across is the following :
>
> $ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 127.0.1.1
>
> It re-writes that file every time a new network connection is made.
>
> $ man resolvconf
> [...]
> DESCRIPTION
> The resolvconf package comprises a simple database for run-time
> name‐
> server information and a simple framework for notifying applications
> of
> changes in that information. Resolvconf thus sets itself up as
> the
> intermediary between programs that supply nameserver information
> and
> applications that use that information.
> [...]
>
> I am not at all sure if this is the cause of the issue, but I have run into
> it many times before with WiFi and me trying to edit it to 8.8.8.8, so I
> figure this is a decent time to bring it up.
- Dave
[Prev in Thread] | Current Thread | [Next in Thread] |