From: Ricardo Wurmus <rekado@elephly.net>
To: Mekeor Melire <mekeor@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: A package search engine for a curated list of channels
Date: Thu, 05 May 2022 11:01:37 +0200 [thread overview]
Message-ID: <87levguz6t.fsf@elephly.net> (raw)
In-Reply-To: <87ilqkykgv.fsf@posteo.de>
Mekeor Melire <mekeor@posteo.de> writes:
> An alternative would be to implement some kind of isolation. But
> channels and package declarations are just scheme/guile code, so they
> will probably always be able to run arbitrary commands on the server.
Guile has some sandboxing features. It would be an option to evaluate
channel modules in a restricted environment with (ice-9 sandbox). That
would benefit all of Guix.
> Another approach would be isolation. For each channel, we could run
> hpcguix-web inside a Docker-container so that there's some isolation.
> Then, we'd need to run another web-service which "bundles" the
> packages.json files of all single-channel, dockerized hpcguix-web
> instances. But:
>
> (1.) Does Docker really offer sufficient isolation?
No more than “guix shell -C”. There’s no good reason to use Docker when
you already have Guix. The Docker service exists for when you have a
Docker container image that you must use, not because its
containerization is superior to “guix shell -C”.
--
Ricardo
next prev parent reply other threads:[~2022-05-05 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:51 A package search engine for a curated list of channels Mekeor Melire
2022-04-27 15:08 ` Edouard Klein
2022-04-27 18:37 ` Ricardo Wurmus
2022-04-27 21:07 ` 404 errors with hpcguix-web (e.g. for /packages.json) Mekeor Melire
2022-05-04 22:25 ` Show: Minimal Working Example of hpcguix-web Mekeor Melire
2022-05-04 22:29 ` A package search engine for a curated list of channels Mekeor Melire
2022-05-05 9:01 ` Ricardo Wurmus [this message]
2022-09-03 10:24 ` zimoun
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=87levguz6t.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=mekeor@posteo.de \
/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.
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).