unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: outlook user <RACP@outlook.fr>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Why Docker instead of PodMan?
Date: Sat, 29 Jun 2024 19:07:33 +0200	[thread overview]
Message-ID: <20240629190733.4ced2cf9@primary_laptop> (raw)
In-Reply-To: <AS8P251MB0854DD63E3E2E5C15E463FA397D12@AS8P251MB0854.EURP251.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Sat, 29 Jun 2024 12:04:31 +0000
outlook user <RACP@outlook.fr> wrote:

> git.savannah.gnu.org/cgit/guix.git/tree/guix/docker.scm

The source code is pretty clear: it doesn't use docker to build the
'docker image'.

If you look at the history of the 'docker image format' in general (not
with a Guix focus) you can see that it probably appeared in docker and
was later standardized as 'OCI' (open container images) but many people
still (only?) know that format as 'docker images'.

So it's not surprising, and the images produced by guix should normally
also work on software like Podman for instance.

A way to make this clear would be to send patches to the documentation.

And while you're at it, there is also the same issue with 'singularity
images' which probably also work with Apptainer. Though here some
distributions already switched to Apptainer so maybe it's also worth
spending time to also add Apptainer to Guix as well, in addition to
patches to improve the documentation.

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-06-29 20:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-29 12:04 Why Docker instead of PodMan? outlook user
2024-06-29 17:07 ` Denis 'GNUtoo' Carikli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240629190733.4ced2cf9@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=RACP@outlook.fr \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).