Hi,
Zhu Zihao skribis:
> "guix environment --container" is a very useful feature for me to
> isolate the untrusted software. But sadly it lacks a interface for user
> to use it in Lisp programming.
The interface to containers is in (gnu build linux-container), though
it’s a bit lower-level comp
Leo Prikler writes:
> For the record, what you do want is something à la
> (call-in-container-environment THUNK MANIFEST . KWARGS)
> where manifest is the Guix environment manifest, THUNK is a procedure
> to call with 0 arguments and KWARGS is a list of options for things you
> might want to set
Am Mittwoch, den 04.11.2020, 18:05 +0800 schrieb Zhu Zihao:
> Leo Prikler writes:
>
> > launch-environment/container still assumes the command to be a
> > shell
> > script, which I think is not quite what you want. You probably
> > want to
> > take a look at call-with-container from (guix build l
Leo Prikler writes:
> launch-environment/container still assumes the command to be a shell
> script, which I think is not quite what you want. You probably want to
> take a look at call-with-container from (guix build linux-container) or
> child-hurds.
I just read the source code of call-with-c
Hello,
Am Mittwoch, den 04.11.2020, 11:49 +0800 schrieb Zhu Zihao
> "guix environment --container" is a very useful feature for me to
> isolate the untrusted software. But sadly it lacks a interface for
> user
> to use it in Lisp programming.
>
> In (guix scripts environment), only `guix-environm
"guix environment --container" is a very useful feature for me to
isolate the untrusted software. But sadly it lacks a interface for user
to use it in Lisp programming.
In (guix scripts environment), only `guix-environment` is exported. but
it process unix style command line option.
I'm wonderin
