From: jgart via Guix-Science <guix-science@gnu.org>
To: guix-science@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: guix-jupyter and allowing network access in isolated containers
Date: Fri, 10 Sep 2021 04:11:39 -0400 [thread overview]
Message-ID: <20210910041139.GB15993@gac.attlocal.net> (raw)
Hi Ludo,
Hope all is well!
I'm messaging here to keep our corespondence public in case it is helpful for others.
An isolated guix-jupyter container does not have access to the internet by default as I read from your blog
post and from the source code of guix-kernel.
What would be the best way to allow networking in a guix-kernel/guix-jupyter isolated container?
Should I be modifying the code for eval/container* in order to create a custom jupyter kernel that allows network access for code run in notebook cells?
Some places were eval/container* is found in the code:
https://gitlab.inria.fr/guix-hpc/guix-kernel/-/blob/master/guix/jupyter/containers.scm#L40
https://gitlab.inria.fr/guix-hpc/guix-kernel/-/blob/master/guix/jupyter/kernel.scm#L181
I'm assuming that the --network command line option won't work with guix-kernel and why I'm
asking about creating my own modified jupyter kernel container instance with network access.
Does it makes sense to have a majic to allow a guix-jupyter notebook user access to the internet?
;;guix allow
like `direnv allow`
or
;;guix network
after the corresponding cli option of `guix environment --network`
I'm interested in this feature for guix-jupyter because I am putting together a demo notebook
showcasing requests to the GeneNetwork REST API.
all best,
jgart
_________________________________________
/ 3B1D 7F19 E36B B60C 0F5B 2CA9 A52A A2B4 \
\ 77B6 DD35 /
-----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
reply other threads:[~2021-09-10 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210910041139.GB15993@gac.attlocal.net \
--to=guix-science@gnu.org \
--cc=jgart@dismail.de \
--cc=ludo@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.
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).