From: "Ludovic Courtès" <ludo@gnu.org>
To: Michal Atlas <michal_atlas+gnu@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: "guix pack -f docker" does too much work
Date: Mon, 17 Jun 2024 13:21:16 +0200 [thread overview]
Message-ID: <87wmmnak7n.fsf@gnu.org> (raw)
In-Reply-To: <fb72b9c2-ea59-9188-8548-24c7877fc42b@posteo.net> (Michal Atlas's message of "Thu, 30 May 2024 13:10:41 +0000")
Hi,
Michal Atlas <michal_atlas+gnu@posteo.net> skribis:
> I greatly agree, it would be an awesome QOL improvement.
If there’s consensus, let’s see how we can get that done. The advantage
of having (guix docker) & co. all in Scheme is that moving it from a
derivation to code running straight from ‘guix pack’ is definitely
feasible (a bit of work though because ‘guix pack’ has quite a few
backends).
> Just want to mention that it might be nice to take inspiration from
> the Nix dockerTools, since they already have quite a lot of effort put
> into this.
>
> Including for example an option called `streamLayeredImage` [1] which
> doesn't generate a tarball at all, but rather a script that outputs
> the layers without assembling them, in a format which Docker or Podman
> can import without the huge intermediary file.
>
> i.e. $(guix pack ...) | docker load
>
> [1]:
> https://ryantm.github.io/nixpkgs/builders/images/dockertools/#ssec-pkgs-dockerTools-streamLayeredImage
Nice! Sounds very much in line with what Ricardo was proposing.
> Also seems that Nix's way only quickly imports the changed layers? And
> Guix's always imports the whole thing, at least I think?
What do you mean by “imports the whole thing”?
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-06-17 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 12:58 "guix pack -f docker" does too much work Ricardo Wurmus
2024-05-30 13:10 ` Michal Atlas
2024-06-17 11:21 ` Ludovic Courtès [this message]
2024-06-17 11:57 ` Michal Atlas
2024-06-17 21:24 ` Ludovic Courtès
2024-06-01 13:58 ` Ludovic Courtès
2024-06-01 19:07 ` Ricardo Wurmus
2024-06-03 7:09 ` Andy Wingo
2024-06-04 18:14 ` Simon Tournier
2024-09-14 14:55 ` Maxim Cournoyer
2024-09-14 18:36 ` Ricardo Wurmus
2024-09-15 0:42 ` Suhail Singh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmmnak7n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=michal_atlas+gnu@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.