From: "Ludovic Courtès" <ludo@gnu.org>
To: 36469@debbugs.gnu.org
Subject: [bug#36469] [PATCH 0/2] 'guix pack' records environment variables
Date: Tue, 2 Jul 2019 10:37:31 +0200 [thread overview]
Message-ID: <20190702083731.10354-1-ludo@gnu.org> (raw)
Hello Guix!
With these patches, images created by ‘guix pack -f docker’ or
‘guix pack -f singularity’ define the right environment variables
for the profile.
For instance, if you do:
guix pack -f docker guile guile-json --entry-point=bin/guile
Then:
docker run THE-IMAGE
will spawn Guile in an environment with $GUILE_LOAD_PATH pointing
to the profile, such that the (json) module is automatically found.
The change for Singularity is similar. I’ve tested it with an
instance of Singularity 3.2.0. Unfortunately, we still have 2.x
in Guix and that doesn’t quite support the environment file, so I’ve
chosen to punt on this one.
Thoughts?
Ludo’.
Ludovic Courtès (2):
pack: 'docker' backend records the profile's search paths.
pack: 'squashfs' backend records the profile's search paths.
gnu/tests/docker.scm | 16 ++++++----
gnu/tests/singularity.scm | 18 ++++++++++-
guix/docker.scm | 17 ++++++++---
guix/scripts/pack.scm | 64 ++++++++++++++++++++++++++++++++++++---
4 files changed, 99 insertions(+), 16 deletions(-)
--
2.22.0
next reply other threads:[~2019-07-02 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:37 Ludovic Courtès [this message]
2019-07-02 8:56 ` [bug#36469] [PATCH 1/2] pack: 'docker' backend records the profile's search paths Ludovic Courtès
2019-07-02 8:56 ` [bug#36469] [PATCH 2/2] pack: 'squashfs' " Ludovic Courtès
2019-07-04 11:17 ` Ricardo Wurmus
2019-07-04 16:12 ` [bug#36469] Name of the Singularity/squashfs backend? Ludovic Courtès
2019-07-04 11:13 ` [bug#36469] [PATCH 1/2] pack: 'docker' backend records the profile's search paths Ricardo Wurmus
2019-07-04 15:06 ` Ludovic Courtès
2019-07-02 16:46 ` [bug#36469] [PATCH 0/2] 'guix pack' records environment variables zimoun
2019-07-04 9:22 ` 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=20190702083731.10354-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=36469@debbugs.gnu.org \
/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).