From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Using Guix inside a Guix container
Date: Mon, 27 Feb 2023 15:27:59 +0100 [thread overview]
Message-ID: <m1v8jntc7k.fsf@fastmail.net> (raw)
In-Reply-To: <87pma2d45z.fsf@gnu.org>
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> That’s an interesting use case! I guess we have a hard-enough time
> getting the message through regarding the environment of tasks that we
> didn’t really consider the environment of the “driver”.
It takes something messy such as Snakemake to illustrate the importance
of this.
> (Well, in a way, GWL and Guix-Jupyter sidestep the issue by integrating
> the mechanism to declare task environments.)
OK, let's pass a law that workflows must be written in Guile or in a
language implemented in Guile ;-)
> I’d be inclined to add a new ‘-W’ (say) option to (1) share the whole
> store, and (2) share the daemon socket. That would be the documented
> way to create a container with support for nested containers.
Sounds good to me!
> That one’s interesting. Reported here:
>
> https://issues.guix.gnu.org/61690
>
> At least there’s a workaround: using ‘-CN’ in the nested container.
That's already good to know.
Thanks,
Konrad.
prev parent reply other threads:[~2023-02-27 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 16:52 Using Guix inside a Guix container Konrad Hinsen
2023-02-03 17:35 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-02-13 11:21 ` James Thomas
2023-02-13 12:35 ` Jim
2023-02-15 9:49 ` Konrad Hinsen
2023-02-17 15:41 ` Simon Tournier
2023-02-18 9:21 ` Konrad Hinsen
2023-03-13 12:52 ` Simon Tournier
2023-02-21 22:50 ` Ludovic Courtès
2023-02-27 14:27 ` Konrad Hinsen [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=m1v8jntc7k.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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).