From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: "guix pack -f docker" does too much work
Date: Mon, 03 Jun 2024 09:09:17 +0200 [thread overview]
Message-ID: <87frtuec4i.fsf@igalia.com> (raw)
In-Reply-To: <87cyp0ojc5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 01 Jun 2024 15:58:50 +0200")
On Sat 01 Jun 2024 15:58, 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.
If the concern is CPU time, I would make sure you have switched to zstd
or some other faster codec, via `guix pack -f docker -C zstd`.
You probably already knew but if you haven't tried, it's quite
surprising :)
Andy
next prev parent reply other threads:[~2024-06-03 7:10 UTC|newest]
Thread overview: 14+ 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
2024-06-03 7:09 ` Andy Wingo [this message]
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
2024-09-26 16:18 ` Simon Tournier
2024-10-05 14:01 ` Maxim Cournoyer
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=87frtuec4i.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).