From: "Ludovic Courtès" <ludo@gnu.org>
To: 36668@debbugs.gnu.org
Subject: [bug#36668] [PATCH 0/1] Add 'eval/container'
Date: Mon, 15 Jul 2019 16:21:26 +0200 [thread overview]
Message-ID: <20190715142126.14612-1-ludo@gnu.org> (raw)
Hello Guix!
This adds ‘eval/container’, which can be used to implement things that
are almost derivation (pure computational processes), but not quite:
processes that produce side effects, that need to access the daemon,
or that need to talk over the network.
It doesn’t have any users currently. Guix-Jupyter-Kernel will probably
use it (to spawn proxied kernels in isolated environments), and I think
Ricardo had a use case for it in GWL too.
What do people think?
I wonder if we should target ‘run-in-container’ instead of
‘call-with-container’, or maybe both. It’s also a bit troubling
that ‘eval/container’ returns an exit status instead of the evaluation
result, but I think it has to be this way, more or less.
Ludo’.
Ludovic Courtès (1):
linux-container: Add 'eval/container'.
gnu/system/linux-container.scm | 49 ++++++++++++++++++++++++++++++++-
tests/containers.scm | 50 ++++++++++++++++++++++++++++++++++
2 files changed, 98 insertions(+), 1 deletion(-)
--
2.22.0
next reply other threads:[~2019-07-15 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 14:21 Ludovic Courtès [this message]
2019-07-15 14:25 ` [bug#36668] [PATCH 1/1] linux-container: Add 'eval/container' Ludovic Courtès
2019-07-15 15:22 ` [bug#36668] [PATCH 0/1] " Thompson, David
2019-07-15 15:51 ` Ludovic Courtès
2019-07-19 9:55 ` bug#36668: " 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=20190715142126.14612-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=36668@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).