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: Tue, 21 May 2019 10:52:49 +0200 [thread overview]
Message-ID: <874l5o5gv2.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ3dvOipKBBr3LdXmQ4T+hU+jXJn+7tB6O+mMUCyJ9zcmg@mail.gmail.com> (zimoun's message of "Mon, 20 May 2019 21:34:32 +0200")
Howdy!
zimoun <zimon.toutoune@gmail.com> skribis:
> On Mon, 20 May 2019 at 17:42, Ludovic Courtès <ludo@gnu.org> wrote:
[...]
>> 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?
>
> Yes, it better fits what I am more or less doing by hand.
> Nice `guix pack` owns this option.
Cool. Note that the advantage is the GC root, but if it’s just about
creating a symlink, you can also do:
ln -s $(guix pack -f docker whatever) my-symlink
>> > 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?
>
> I was proposing:
> guix pack -f docker -r foo
> generates the file:
> /gnu/store/<long-hash>-docker-pack.tar
> where the symlink foo to this file and the field REPOSITORY should be
> guix and the field TAG should `foo-<short-hash>` where <short-hash>`
> is let say 6 characters.
OK.
> I do not know if it is the right way. What do people using Docker think ?
Yup, I’m curious what people think best practice is! Because I don’t
really qualify as a “Docker user” myself. :-)
Thank you,
Ludo’.
prev parent reply other threads:[~2019-05-21 8:52 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
2019-05-20 19:34 ` zimoun
2019-05-20 20:02 ` Ricardo Wurmus
2019-05-21 8:52 ` Ludovic Courtès [this message]
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=874l5o5gv2.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).