Received: from mail.redxen.eu (chisa.nurnberg.hetzner.redxen.eu [IPv6:2a01:4f8:c2c:b2fc::1])
	by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 63DD122363D
	for <~alpine/devel@lists.alpinelinux.org>; Sun, 18 Jun 2023 09:02:01 +0000 (UTC)
Received: from localhost (karu.nurnberg.hetzner.redxen.eu [157.90.160.106])
	by mail.redxen.eu (RedXen Mail Postfix) with ESMTPSA id EDA8A5FA66;
	Sun, 18 Jun 2023 09:01:57 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=redxen.eu;
	s=2021.05.31.01-mail; t=1687078918;
	bh=aw5hn0NVg1oCSzNMl09nkWiNq6te9caXf/EHN9FQ8UQ=;
	h=Date:To:Cc:Subject:From:References:In-Reply-To;
	b=csSWeteAnuj7PyMJb15OVzwHBRgI37TQG4tE4vSab6xv3shEu59A1XdSb9KfBzQVG
	 qMLcK6E8HfTWqpF3hf3B1OsW7mWfcpUs3jtAkrQ1lhydMpnM2qpLOtrqtox3aTceam
	 AjV3zQ3TQLOAECx1IjYTJiYBilrrHaBimAweSIXdo1lgMThdUMc+EcRt3WuhvFf3Fk
	 OF69xU/hCE70NGfx4vpMwIuzdpEwyLHS9jjSrmoin9Jyys6PbkKno48abHyjw2OdHR
	 a9LNPujMTDVQG/43IjZ/ynjYfibEY/HgjQk1pMp26kSjUrvJPvPEKbUxptIUP+EDxG
	 gup6kDYKKzq0w==
Authentication-Results: mail.redxen.eu;
	auth=pass smtp.auth=caskd smtp.mailfrom=caskd@redxen.eu
Date: Sun, 18 Jun 2023 09:01:57 +0000
To: alice <alice@ayaya.dev>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: IPv6 DNS in docker.io/alpine
From: caskd <caskd@redxen.eu>
References: <2S4UGX2K2XUWW.383MIJ9QU1RGG@unix.is.love.unix.is.life>
 <CTFDHUVT80YL.BFAWP2B748KE@sumire>
In-Reply-To: <CTFDHUVT80YL.BFAWP2B748KE@sumire>
Message-Id: <2NT12AEIPXQS6.2JTIOVIOSLPHN@unix.is.love.unix.is.life>
User-Agent: mblaze/20220328-3140-g8658ea6aef
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="----_=_1424c8a8169122163f24ed5c_=_"

This is a multipart message in MIME format.

------_=_1424c8a8169122163f24ed5c_=_
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_6ec3de4b3f30c46568d0d387_=_"

This is a multipart message in MIME format.

------_=_6ec3de4b3f30c46568d0d387_=_
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> isn't the resolv.conf in a started container populated on start depending=
 on the
> networking configuration?
>=20
> e.g. with --network=3Dhost it just uses your current /etc/resolv.conf. wi=
thout it,
> it depends on how the networking for containers is set up, ...
>=20
> the actual images are just the unpacked minirootfs, made with mkimg.minir=
ootfs.sh,
> but i don't think that touches resolv.conf at all.
Indeed. I've started looking deeper and completly missed the upper layer wh=
ere the actual change happens. This is irrelevant now.

--=20
Alex D.
RedXen System & Infrastructure Administration
https://redxen.eu/

------_=_6ec3de4b3f30c46568d0d387_=_--

------_=_1424c8a8169122163f24ed5c_=_
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQJEBAABCgAuFiEE2k4nnbsAOnatJfEW+SuoX2H0wXMFAmSOyAQQHGNhc2tkQHJl
ZHhlbi5ldQAKCRD5K6hfYfTBc1nOD/9Djg0p8oKxqaWgI6k66/ge2sKAQ15hjD6Y
ydbGrjVXoqtET40Jm/3u2Aktcm9QnZttjd/RDOOJqS82BNeptvVGTIiVMj9N4l2L
SmUKFxVa8dKxxg/2AbLc0ZkfpjjadybAGSGb2UwPca5Sxd3DAig0mMa2LxiIqrlJ
nP9VNwwXDB14lEfHK/+wM4bXfnlcpODoU06ynfKehQBHQ5mifHiMkYqpOIsAQNaH
Rl7DsN7iI+IRdFaUDaLtg6BblAx6iDc1gE5mxd4at+sZhyG6Z9+LiFYxKupruQwb
g9wiX0JaTqMCG+XV7dQ4EB3givAJNqG6EhI72ehtit8n1lWkeIxgg5774w1gE7KK
+3KBY7MOH4fHbIq6ju7PdgI6aRptjFgeGgAjsgoWHJX+i65knM+jpV2ck003xtaU
KiNLbzi6P7fbwfiAGlWJvU137mP1AtnTwicVK3xidvW2gdenTjE0o+3nTl7/Vg8D
SkLzA92j2txdW/hEOSLH6e8iur8RGpfkPQ3SXGpxkQJDAQ/vcmqNwR2hQfyqhXcY
BJTBbXPInB5BMdjtFVxiSgVWeI6LSgE7nKBjEy6/r+jvZUUPpzN25cxIFB04xjuY
+obdGmI6HEzrVRpl+JJNfpiMkKTXxPXTb5EfID0lrRFXa365hHWQwiMAgRuwg8th
9OymRPEuoQ==
=0OmH
-----END PGP SIGNATURE-----

------_=_1424c8a8169122163f24ed5c_=_--