From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id mH0NNycb6WMfeAAAbAwnHQ (envelope-from ) for ; Sun, 12 Feb 2023 18:00:23 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 8LH0Nicb6WOQKAEAauVa8A (envelope-from ) for ; Sun, 12 Feb 2023 18:00:23 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 80196D418 for ; Sun, 12 Feb 2023 18:00:23 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pRFhx-00062o-CO; Sun, 12 Feb 2023 12:00:09 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pRFht-00062b-Er for bug-guix@gnu.org; Sun, 12 Feb 2023 12:00:05 -0500 Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pRFhr-0000Wj-LA for bug-guix@gnu.org; Sun, 12 Feb 2023 12:00:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pRFhr-0001mM-Bk for bug-guix@gnu.org; Sun, 12 Feb 2023 12:00:03 -0500 X-Loop: help-debbugs@gnu.org Subject: bug#51505: Request for official docker image on dockerhub References: In-Reply-To: Resent-From: Denis 'GNUtoo' Carikli Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Sun, 12 Feb 2023 17:00:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51505 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: 51505@debbugs.gnu.org Received: via spool by 51505-submit@debbugs.gnu.org id=B51505.16762211556715 (code B ref 51505); Sun, 12 Feb 2023 17:00:03 +0000 Received: (at 51505) by debbugs.gnu.org; 12 Feb 2023 16:59:15 +0000 Received: from localhost ([127.0.0.1]:46536 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pRFh4-0001kE-II for submit@debbugs.gnu.org; Sun, 12 Feb 2023 11:59:15 -0500 Received: from cyberdimension.org ([80.67.179.20]:44812 helo=gnutoo.cyberdimension.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pRFh2-0001k5-LN for 51505@debbugs.gnu.org; Sun, 12 Feb 2023 11:59:13 -0500 Received: from gnutoo.cyberdimension.org (localhost [127.0.0.1]) by cyberdimension.org (OpenSMTPD) with ESMTP id cff5b923 for <51505@debbugs.gnu.org>; Sun, 12 Feb 2023 16:55:38 +0000 (UTC) Received: from primary_laptop (localhost [::1]) by gnutoo.cyberdimension.org (OpenSMTPD) with ESMTP id 68e6d074 for <51505@debbugs.gnu.org>; Sun, 12 Feb 2023 16:55:38 +0000 (UTC) Date: Sun, 12 Feb 2023 17:57:24 +0100 From: Denis 'GNUtoo' Carikli Message-ID: <20230212175724.5815d1fb@primary_laptop> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.30; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/jqf3ypHxwrz9DhtcCVrc1_q"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Seal: i=1; s=key1; d=yhetil.org; t=1676221223; a=rsa-sha256; cv=none; b=e3ri342wqaswnCLml1ITYL3Us63VoVvZ6CuI09J5y+nFsG8Qp6yp102930x5sSdGmjsyh8 86fMyHxeizwbCc0GtD5kysFoI+oBjXcqmtQdDjWhF5JEWlVRveELIv7I55nA0JMWTuaTsE t0QiGR4Fma0nLE9jGqnqrZQ7NgK9F4b0QXEvWw706xh4fJ9Kd3fULwXtwAsch9bshAj6SK 9fg4oRO73C5XJ47GL6QzjMU6g/II1AzxXF9lVXKMzjickfn59J6rqNEGxsoDQ+E00DFXOn iEjVfSG+AlyDxQy2Rxps0f+YVFe9TbxZigoprVSunQ24x4fv7wXM0MeVBPwJSg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1676221223; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:resent-cc:resent-from:resent-sender: resent-message-id:in-reply-to:in-reply-to:references:references: list-id:list-help:list-unsubscribe:list-subscribe:list-post; bh=ompmp4MrEBDHvA474Noo6iyvO3fW9P51J74A401mdW8=; b=W4iPGUun4UAtjFUtpaRU+V9xjcOVhxQlhI7GZmorQMMxEVYfADTza1dCGGsJxn6Xwf0z4h LeimkRDBKhUHqkvk7hcoGpfpnFxNuXudYJlvm1QeyPObIMNNDkAKuzjqG4FFKTRYfsveca GpfRGd3NrVghJyiPIsYt+YChVHLJcZRcrD8lm2bFU9HMcOlXuVlpY24iIe7ospK/AL+ply JJQ7g1IzLpB8WwU2NbZr1SRzTsldSivMhNrmM2IPWhmRn7NmP9CoCJmWlF60kahXQ92YYN 3afMbr6kH+/ZNTOSi/1E+QnH8tYLE7HmZrFjdVSHcrfVl+Ci4pfBIpvnYPWb4A== X-Migadu-Spam-Score: -5.47 X-Spam-Score: -5.47 X-Migadu-Queue-Id: 80196D418 X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=none; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none X-TUID: 7LxjiBeB/zRK --Sig_/jqf3ypHxwrz9DhtcCVrc1_q Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, If the idea is to be able to use a Guix docker image, as I understand dockerhub is not strictly required. For instance Fedora has its own docker registry[1] that works out of the box with docker pull. More generally to download an image one can just run: 'docker pull /'. As I understand that is usable in Dockerimages in the same way. If I understood well, your issue is to integrate Guix docker images in test environments that require you to use only a Dockerfile. For publishing Guix docker images, Guix has several options that are not mutually exclusive: - It could use dockerhub. Note that the dockerhub registry/repository itself is not FSDG compliant as it contains nonfree software like Windows images. - Guix could setup its own docker registry. There is a work in progress patch for the docker registry (bug #60770) that works but it still needs to un-vendor the dependencies. We also need to look how to use it to deploy public registries (I've only tested it on localhost so far, so without certificates and authentication). Also nobody reviewed that patch yet and there seems to be a huge backlog with patches review. - Someone could setup a general FSDG compliant registry for various docker images, and Guix could add official images there. - Someone could also do some research to see if it's possible to host images on a simple web server and make docker think it's a registry. If that works, it could integrate well with guix.gnu.org/en/download and guix.gnu.org/en/download/latest and the Guix release infrastructure. Though one issue here is that docker somehow expects yaml files on directory paths. If Guix uses a third party registry, the third party will not have the same policies and priorities than Guix. And in practice the third party will be able to modify the images, as it hosts images that lack signatures, and as far as I know there is also no way to automatically verify some signatures before running the images. PureOS also uses dockerhub, and as far as I know their docker images are FSDG compliant. So if you need FSDG compliant images you could use that and download and run Guix there. Parabola and Trisquel also have what is needed to make docker images but the images are not published anywhere as far as I know, so other FSDG compliant distributions didn't really solve the issue either. Alternatively Guix could just publish additional docker images in guix.gnu.org/en/download and guix.gnu.org/en/download/latest but here I guess that this doesn't work for your test environment. As for the Debian images you mentioned they are somehow semi-official according to Debian. Maybe it's because they are made by some Debian maintainers and are not part of the regular Debian release process. Personally I'd like to be able to use docker and more specifically Dockerfiles in an FSDG compliant and trustworthy way, so I've started looking a bit into it, for all FSDG compliant distributions in general[2], but we have no drop-in solution that integrate well with distributions release processes yet. Also note that I'm new to docker so I might have missed some stuff, and I'm also not a Guix maintainer so I can't take decisions for the Guix project. References: ----------- [1]https://registry.fedoraproject.org It is probably not FSDG compliant. [2]https://libreplanet.org/wiki/Group:Software/research/ExternalRepositorie= s/DockerRegistries Denis. --Sig_/jqf3ypHxwrz9DhtcCVrc1_q Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEeC+d2+Nrp/PU3kkGX138wUF34mMFAmPpGnQACgkQX138wUF3 4mM86g/+OH/rEh4mnEN5OcSZ0mZSVWTHJSoUrnuPPyC3L6sGvP9m/yNVb0GTen9q YYeJ6cUcoq9zF27iSAIetr1LQBE7UmrVUVjcVKvXRU4tkA2ia1zXjVKuVSkqg6vA XKVTGqrSEP0Y6gV/rtLvmRvSekrnbiAYDxJw08OezY6XLajVHjVgtZwr+01EqBwi emFfQlm3PiSdmVpZrfGe5yareOLfPx3DJGolL9dpYjWNQJVT2jO5NDI0AJx7uCkl vKA1QyIdsrUVmOy65FK6JEV2wstRg3q56oFlzcLqKvQVqFAhrIfUAIo816IfqBmZ SavfAeoozMN7Tv7hh5ny2ad6FXtBhotH3u/nXu6KnVcntHVSHOOUCAGMJxWWvx4/ oLzN3DtZu+Muyr99BJEbnx5aeulHrAcJKDK1jaKgbLmnME7Q/jvuWYQeyvdWOGw5 R7GAQFg7WSW+x+NszqTrIl7aNQp2xnop3kmsFiTtlBpzZ+opM0xyhBMPj87IGpBc hFQhRC/DE/hHNxGqoBefA18zm5xXFOF/FNr8LzLFF2EL1M9dmrNVlj8Eo4e01xY8 oEj6oWq21/A87qtjvIgm/lvUa0XqFb+nn3dcTOqODBXknU3nBiifvGOqnOeflrXX RFEbXhA+0HBjKe7/B2DRmTsYJX/r5nmCKhCV8pDA9EdlsRxtlEk= =kj7R -----END PGP SIGNATURE----- --Sig_/jqf3ypHxwrz9DhtcCVrc1_q--