From: Greg Hogan <code@greghogan.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Przemysław Kamiński" <cgenie@pm.me>, help-guix@gnu.org
Subject: Re: specify custom manifest->friendly-name for guix pack -f docker?
Date: Fri, 20 Jan 2023 10:07:57 -0500 [thread overview]
Message-ID: <CA+3U0Zn72btL7h0HzzF9WgXXN0aosUTBhpVBcvhpBEuBmRjrwA@mail.gmail.com> (raw)
In-Reply-To: <87h6wlqurx.fsf@gmail.com>
On Fri, Jan 20, 2023 at 7:18 AM Simon Tournier <zimon.toutoune@gmail.com> wrote:
>
> > Maybe then add an option to guix pack to accept optional name? And if not
> > provided, fall back to manifest->friendly-name.
>
> …yes, I agree. It could be nice to be able to directly name the image.
> However, this would mean that the produced Docker pack would not be
> bit-to-bit reproducible considering the same manifest. Other said, the
> bit-to-bit reproducibility would require three inputs: the channels.scm
> file describing the revision of Guix (and potentially other channels),
> the manifest.scm file describing the packages and also the name provided
> at Docker pack build-time.
>
> Cheers,
> simon
The image hash already depends on `guix pack` command-line options
--entry-point, --save-provenance, and --symlink as well as package
transformations, --no-grafts, and --system. Since building a
bit-to-bit reproducible docker image already requires replaying the
command-line options, adding an optional name would not reduce
reproducibility.
Greg
next prev parent reply other threads:[~2023-01-20 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 20:40 specify custom manifest->friendly-name for guix pack -f docker? Przemysław Kamiński via
2023-01-20 12:01 ` Simon Tournier
2023-01-20 15:07 ` Greg Hogan [this message]
2023-01-20 17:15 ` Przemysław Kamiński via
2023-02-13 9:11 ` 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
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=CA+3U0Zn72btL7h0HzzF9WgXXN0aosUTBhpVBcvhpBEuBmRjrwA@mail.gmail.com \
--to=code@greghogan.com \
--cc=cgenie@pm.me \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).