From: Ricardo Wurmus <rekado@elephly.net>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: Andy Wingo <wingo@pobox.com>, guix-devel <guix-devel@gnu.org>
Subject: Re: Introducing ‘guix pack’
Date: Mon, 20 Mar 2017 16:14:57 +0100 [thread overview]
Message-ID: <87shm8f09a.fsf@elephly.net> (raw)
In-Reply-To: <87a88grpws.fsf@lassieur.org>
Clément Lassieur <clement@lassieur.org> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello Guix! Hello 2.2 Guilers!
>>
>> ludo@gnu.org (Ludovic Courtès) skribis:
>>
>>> I’d like to move support for Docker (currently in ‘guix archive’) to
>>> this new command because I think it’s more appropriate: ‘guix archive’
>>> is supposed to be rather low-level so it would not create a profile, for
>>> instance.
>>
>> As of right now, ‘guix pack’ can create Docker image (‘guix archive’
>> can no longer do that):
>>
>> guix pack guile-next -S /opt/guile-2.2.0= -f docker
>>
>> I’d be grateful if someone could check with Docker that I didn’t break
>> anything though. Any takers? :-)
>
> I just tested it (although I'm probably not the first) and it works
> (with "docker load"). Thanks!
I also tested it successfully:
image=$(guix pack -f docker -S /opt/gnu/bin=bin r)
docker load < $image
id=$(docker images -q profile | tail -n 1)
docker run --rm --tmpfs /tmp:rw,size=787448k,mode=1777 -ti $id /opt/gnu/bin/R
This creates an image for R, loads it, starts (and eventually removes)
a container in which R runs.
For people who find this cumbersome: use containers with Guix instead.
Here’s how:
guix environment --container --ad-hoc r -- R
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-03-20 15:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 21:50 Introducing ‘guix pack’ Ludovic Courtès
2017-03-10 23:43 ` Ricardo Wurmus
2017-03-11 21:05 ` Chris Marusich
2017-03-12 16:56 ` Ludovic Courtès
2017-03-12 23:03 ` Ricardo Wurmus
2017-03-13 7:44 ` Chris Marusich
2017-03-13 10:18 ` Andy Wingo
2017-03-14 13:42 ` Ludovic Courtès
2017-03-14 14:00 ` Andy Wingo
2017-03-14 17:02 ` Ludovic Courtès
2017-03-19 17:13 ` Federico Beffa
2017-03-19 22:56 ` Ludovic Courtès
2017-03-20 8:09 ` Federico Beffa
2017-03-20 14:14 ` Ludovic Courtès
2017-03-21 10:48 ` Andy Wingo
2017-03-22 8:48 ` Federico Beffa
2017-03-24 9:56 ` Ludovic Courtès
2017-03-20 14:16 ` Ludovic Courtès
2017-03-20 15:16 ` Alex Sassmannshausen
2017-03-16 22:28 ` Ludovic Courtès
2017-03-17 17:23 ` Pjotr Prins
2017-03-17 23:43 ` Ludovic Courtès
2017-03-17 23:49 ` Ludovic Courtès
2017-03-19 12:01 ` Jan Nieuwenhuizen
2017-03-20 14:20 ` Clément Lassieur
2017-03-20 15:14 ` Ricardo Wurmus [this message]
2017-03-20 15:41 ` 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=87shm8f09a.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=wingo@pobox.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).