From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix pack -f docker and name ?
Date: Mon, 20 May 2019 17:42:10 +0200 [thread overview]
Message-ID: <877ealqgj1.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ3P8ypPy=AcFemGAfZ9GCiB4LM4rdJN-vtNw3k4P+1OMg@mail.gmail.com> (zimoun's message of "Thu, 16 May 2019 20:47:17 +0200")
Hi Simon,
zimoun <zimon.toutoune@gmail.com> skribis:
> 1.
> The name of the tar is given at the end of the command `guix pack`. If
> you forget to track it, then you need to re-run `guix pack` (obviously
> with the very same parameters) to get it again.
> It is not super user-friendly. :-)
>
> What to think to add an option to name a symbolic link to this file in
> the store ?
>
> Currently, I am doing that by hand:
> guix pack -f docker ...
> # copy the name /gnu/store/<hash>-docker-pack.tar
> ln -s paste my-name
>
> In general, I choose my-name as <foo-bar>-<hash> with <foo-bar>
> something to quickly remember what it is and the <hash> to be sure of
> what it is.
I think ‘guix pack’ should have a ‘-r/--root’ option like ‘guix build’
so you can do:
guix pack -r my-image -f docker foo bar baz
WDYT?
> 2.
> Once loaded with `docker load < /gnu/store/<hash>-docker-pack.tar`
> then `docker image ls` list all the images. The REPOSITORY and TAG are
> not super helpful. :-)
> It is always: profile and <hash>.
>
> Maybe REPOSITORY should be guix and TAG should be <short-hash>-<name>.
> Because when one has more than 2 images, after holidays it is not
> possible to remember or they needs to track in a separate file what it
> is.
I agree, we can do better here. :-)
We could allow for user-provided names, and/or, when ‘--save-provenance’
is used, we could show the commit ID or something.
Ideas?
You’ve already proposed other improvements to ‘guix pack -f’, and I
think you should email a concise reminder to each specific improvement
to bug-guix so we keep track of them. I may be able to work on them
soonish.
Thank you!
Ludo’.
next prev parent reply other threads:[~2019-05-20 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 18:47 guix pack -f docker and name ? zimoun
2019-05-20 15:42 ` Ludovic Courtès [this message]
2019-05-20 19:34 ` zimoun
2019-05-20 20:02 ` Ricardo Wurmus
2019-05-21 8:52 ` Ludovic Courtès
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=877ealqgj1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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.
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).