Received: from out-47.mta1.migadu.com (out-47.mta1.migadu.com [IPv6:2001:41d0:203:375::2f])
	by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id E2AB9223650
	for <~alpine/devel@lists.alpinelinux.org>; Sun, 18 Jun 2023 01:08:38 +0000 (UTC)
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ayaya.dev; s=key1;
	t=1687050516;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=bNgUMJAvSPlyn0GVhGCeUh9UuH/LOB1hhQovKN4dGQc=;
	b=XWmGr0SUjloV2pfIjsei5bDOnJCJFLcHeBauypDheEYCXflz749sksOCpmYg8ju4URQdqX
	jtrCO03Apax40/GYcy+yokQWnfXCk0K4ec8TtojK5xaXcS3MLQiUjo/ZZ1u8lMGkRa5Q3E
	+lRzuQ3B06RBcOhE1YC/C9M+d6rXGes=
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Sun, 18 Jun 2023 03:08:34 +0200
Message-Id: <CTFDHUVT80YL.BFAWP2B748KE@sumire>
Subject: Re: IPv6 DNS in docker.io/alpine
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: "alice" <alice@ayaya.dev>
To: "caskd" <caskd@redxen.eu>, <~alpine/devel@lists.alpinelinux.org>
References: <2S4UGX2K2XUWW.383MIJ9QU1RGG@unix.is.love.unix.is.life>
In-Reply-To: <2S4UGX2K2XUWW.383MIJ9QU1RGG@unix.is.love.unix.is.life>
X-Migadu-Flow: FLOW_OUT

On Fri Jun 16, 2023 at 12:33 PM CEST, caskd wrote:
> Hello everyone,
>
> i've been trying to pin down where the resolv.conf in the docker image
> is coming from without success. I've been looking into submitting a reque=
st
> to add IPv6 addresses to the default too to allow containers with IPv6 on=
ly
> connectivity to resolve without deriving a image from the base.
>
> Could you help me pin down where the build scripts/Dockerfile for these a=
re
> and would adding IPv6 as a fallback cause problems?

isn't the resolv.conf in a started container populated on start depending o=
n the
networking configuration?

e.g. with --network=3Dhost it just uses your current /etc/resolv.conf. with=
out it,
it depends on how the networking for containers is set up, ...

the actual images are just the unpacked minirootfs, made with mkimg.miniroo=
tfs.sh,
but i don't think that touches resolv.conf at all.