From: Simon Tournier <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
Guix Devel <guix-devel@gnu.org>, James Thomas <jimjoe@gmx.net>,
Jim <jimplyl@outlook.com>
Subject: Re: Using Guix inside a Guix container
Date: Fri, 17 Feb 2023 16:41:59 +0100 [thread overview]
Message-ID: <87a61c5mew.fsf@gmail.com> (raw)
In-Reply-To: <m13577cl6r.fsf@fastmail.net>
Hi Konrad,
On mer., 15 févr. 2023 at 10:49, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> That would create a container from the Guix profile. Not sure if this
> works at all, but it's very probably not what I want because I have to
> add other packages to my container, to get some real work done :-)
I am sure you have good reasons for doing this and I am lacking
imagination to find them. :-)
Which part of Guix do you need inside the containerized shell that you
cannot do outside?
Basically, you are authorizing the inside Guix to behave with the same
permissions as the outside Guix; therefore, why this dance?
Well, I understand the needs for running inside a containerized shell:
restricted permissions on filestystem, use of --emulate-fhs for allowing
untrusted binaries, etc.
But I miss what is the need to run Guix inside a containerized shell
where it has the permissions as the non-containerized shell.
Considering your use-case with Snakemake, what I am doing is to wrap
each rule with one containerized Guix shell which controls the
permissions, rule by rule; or a big containerized shell:
guix shell -C -m manifest.scm --expose=…
where manifest.scm contains the tools of each rule and snakemake.
Could you provide some details about why you also need Guix?
Cheers,
simon
next prev parent reply other threads:[~2023-02-17 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 16:52 Using Guix inside a Guix container Konrad Hinsen
2023-02-03 17:35 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-02-13 11:21 ` James Thomas
2023-02-13 12:35 ` Jim
2023-02-15 9:49 ` Konrad Hinsen
2023-02-17 15:41 ` Simon Tournier [this message]
2023-02-18 9:21 ` Konrad Hinsen
2023-03-13 12:52 ` Simon Tournier
2023-02-21 22:50 ` Ludovic Courtès
2023-02-27 14:27 ` Konrad Hinsen
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=87a61c5mew.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jimjoe@gmx.net \
--cc=jimplyl@outlook.com \
--cc=konrad.hinsen@fastmail.net \
/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).