From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: "guix pack -f docker" does too much work
Date: Sat, 01 Jun 2024 21:07:43 +0200 [thread overview]
Message-ID: <87plt0jxc0.fsf@elephly.net> (raw)
In-Reply-To: <87cyp0ojc5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 01 Jun 2024 15:58:50 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
>> I think it would be great if "guix pack -f docker" could avoid building
>> all these identical layers again and again. Perhaps it would be
>> possible to have a single derivation for each layer? This way we
>> wouldn't have to recreate the same layer archives every time.
>
> That sounds nice in terms of saving CPU time. It’s less nice in terms
> of disk usage: a single ‘guix pack -f docker’ run would populate the
> store with roughly twice the size of the closure.
Arguably we don't actually care all that much for the Docker image that
ends up in the store. It's really a temporary thing that we want to
load into Docker or upload somewhere else. I've often wanted to stream
the eventual output of "guix pack" to a pipe, precisely because I don't
want to store the same thing twice: once in the store and once in the
Docker storage backend.
It's actually worse than that: I often end up having dozens of packs in
the store whose layers are almost all identical.
> I think each solution (single derivation vs. one derivation per layer)
> makes a different tradeoff. I don’t have a strong feeling about which
> one is better.
Can we have both? I realize that adding the option to stream build
output to a pipe is not a trivial change, but it would solve the
unnecessary storage requirement for packs. "docker load" reads from
standard input, but other packs would also benefit from a streaming
output; an example is Docker-free deployment to a remote server: just
pipe "guix pack" to a remote tar process and you're all set.
--
Ricardo
next prev parent reply other threads:[~2024-06-01 19:08 UTC|newest]
Thread overview: 9+ 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
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 [this message]
2024-06-03 7:09 ` Andy Wingo
2024-06-04 18:14 ` Simon Tournier
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=87plt0jxc0.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
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.