From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:47783) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hn2pj-0002Yd-RQ for guix-patches@gnu.org; Mon, 15 Jul 2019 11:24:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hn2pf-0002A3-0Q for guix-patches@gnu.org; Mon, 15 Jul 2019 11:24:07 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:39964) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hn2pe-00029y-TC for guix-patches@gnu.org; Mon, 15 Jul 2019 11:24:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hn2pe-0006RZ-Oe for guix-patches@gnu.org; Mon, 15 Jul 2019 11:24:02 -0400 Subject: [bug#36668] [PATCH 0/1] Add 'eval/container' Resent-Message-ID: MIME-Version: 1.0 References: <20190715142126.14612-1-ludo@gnu.org> In-Reply-To: <20190715142126.14612-1-ludo@gnu.org> From: "Thompson, David" Date: Mon, 15 Jul 2019 11:22:44 -0400 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 36668@debbugs.gnu.org Hi Ludo, On Mon, Jul 15, 2019 at 10:22 AM Ludovic Court=C3=A8s wrote: > > Hello Guix! > > This adds =E2=80=98eval/container=E2=80=99, which can be used to implemen= t 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=E2=80=99t have any users currently. Guix-Jupyter-Kernel will pr= obably > 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? This is great. Love to see 'call-with-container' used for new things. > I wonder if we should target =E2=80=98run-in-container=E2=80=99 instead o= f > =E2=80=98call-with-container=E2=80=99, or maybe both. I am behind the times. What is special about 'run-in-container'? > It=E2=80=99s also a bit troubling > that =E2=80=98eval/container=E2=80=99 returns an exit status instead of t= he evaluation > result, but I think it has to be this way, more or less. I haven't looked at your code, but have you considered supporting return values that can be serialized via 'write' and then using 'read' on the host side? (Hmm, I wonder how exceptions could be passed from container to host.) Anyway, nice work! - Dave