From: Simon Tournier <zimon.toutoune@gmail.com>
To: gwl-devel@gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>
Subject: Containerized workflow in containerized processes
Date: Mon, 13 Mar 2023 13:50:32 +0100 [thread overview]
Message-ID: <87wn3klsrr.fsf@gmail.com> (raw)
In-Reply-To: m1r0unuy4v.fsf@fastmail.net
Hi,
From thread in guix-devel:
Using Guix inside a Guix container
Sat, 18 Feb 2023 11:01:50 +0100
id:m1mt5uk7y1.fsf@fastmail.net
https://yhetil.org/guix/m1mt5uk7y1.fsf@fastmail.net/#r
The use-case “Containerized workflow in containerized processes” appears
to me interesting. :-)
It is almost done by design with GWL, no?
-------------------- Start of forwarded message --------------------
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Simon Tournier <zimon.toutoune@gmail.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Using Guix inside a Guix container
Date: Sat, 18 Feb 2023 10:21:52 +0100
Hi Simon,
> Which part of Guix do you need inside the containerized shell that you
> cannot do outside?
That's not the right question. There's always a way to do what I want to
do outside. But that may be very inconvenient.
> 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=…
Nice example. I do the same: "guix shell" in every rule. Then I add
stuff to my Snakefile, which is a Python script after all. For example,
I import pandas to read a data frame from which I construct my workflow.
Now I am at the point where I'd like to run snakemake itself in a
container, to manage the dependencies of my Snakefile. In fact, given
that I have workflows that depend on specific Snakemake versions, I'd
really like to run Snakemake in a container all the time, even without
additional dependencies.
Without nested containers, I have to go through all the rules, collect
the packages from their manifest files (or command line), and add them
to the container in which I run the whole workflow. Possible, but not
convenient.
Another example: I run command-line programs from my Pharo image, and I
have developed the habit of doing this always through Guix. The
advantage is that my Pharo code becomes portable: it depends on Guix,
but not on my profile.
But if I want, one day, to move on to a full Guix system, I have to run
Pharo in a container with LFS simulation. And then all my command line
shell-outs will break.
Both examples are about composing tools freely, without worrying if they
use Guix internally or now.
Cheers,
Konrad
-------------------- End of forwarded message --------------------
Cheers,
simon
next parent reply other threads:[~2023-03-13 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1r0unuy4v.fsf@fastmail.net>
2023-03-13 12:50 ` Simon Tournier [this message]
2023-03-21 8:13 ` Containerized workflow in containerized processes 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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn3klsrr.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.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.
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).