Re: specify custom manifest->friendly-name for guix pack -f docker?
Or, just a wild idea: maybe make xspecirl" manifest entries that would modify Docker image? This actually would resemble the Dockerfile: name, entrypoint, package installs and custom script execution is done in one fine, streamlined. It seems a bit strange for me, for example, to specify things like entrypoint on the guix pack command line. Best, Przemek Sent from Proton Mail mobile \ Original Message On Jan 20, 2023, 16:07, Greg Hogan < c...@greghogan.com> wrote: > > On Fri, Jan 20, 2023 at 7:18 AM Simon Tournier 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 publickey - EmailAddress(s=cgenie@pm.me) - 0x9CC42B0A.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: specify custom manifest->friendly-name for guix pack -f docker?
On Fri, Jan 20, 2023 at 7:18 AM Simon Tournier 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
Re: emacs-guix: error message when calling guix-packages-by-name
Hi, André A. Gomes writes: > Hi Guix, > > When running the command guix-packages-by-name from emacs-guix I get the > following error: > > Starting Guix REPL ... [5 times] > guix-geiser-eval: Error in evaluating guile expression: > ice-9/boot-9.scm:1685:16: In procedure raise-exception: > In procedure package-name: Wrong type argument: # gnu/packages/abduco.scm:28 7ff3e7236f20> > > Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue. > scheme@(emacs-guix) [1]> Invalid face reference: sly-inspector-label-face > > I'm wondering whether this is general problem or a problem from my > side. Thanks. I just tried it, and it seems to work here. -- Thanks, Maxim
Re: specify custom manifest->friendly-name for guix pack -f docker?
Hi, On mer., 18 janv. 2023 at 20:40, Przemysław Kamiński via wrote: > that produces cryptic docker image names like bash-coreutils-r-zhs. Well, this is an improvement compared to the previous behaviour. :-) See 0074844366381e3056d09492b8b437836c7adb61: --8<---cut here---start->8--- pack: Provide a meaningful "repository name" for Docker. Previously, images produced by 'guix pack -f docker' would always show up as "profile" in the output of 'docker images'. With this change, 'docker images' shows a name constructed from the packages found in the image--e.g., "bash-coreutils-grep-sed". --8<---cut here---end--->8--- And one thing discussed at the time of this change was that the rename for a more meaningful name could append on the Docker side. That’s said… > 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
