From: Simon Tournier <zimon.toutoune@gmail.com>
To: Kyle Andrews <kyle@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: guix pack isolation
Date: Thu, 16 Feb 2023 10:44:00 +0100 [thread overview]
Message-ID: <86cz6ac5cv.fsf@gmail.com> (raw)
In-Reply-To: <87cz6ao2n0.fsf@posteo.net>
Hi,
On Wed, 15 Feb 2023 at 23:56, Kyle Andrews <kyle@posteo.net> wrote:
>> I do not have Singularity at hand, let demo with Docker
>> which is very similar.
>
> Too bad! My system admistrators are against running Docker on the
> cluster. The "relocatable" option didn't seem relevant to me since it
> wouldn't apply any file system isolation.
Well, I think it should not be an issue for Singularity to reuse Docker
pack. ;-) Once the Docker pack imported inside Docker – say e.g., docker
load < $(guix pack -f pack …) – then something like,
singularity run docker://python-python-numpy-bash:latest python3
should do the job. Anyway! :-)
>> $ docker run -ti python-python-numpy-bash:latest python3
>
> The arguments in this command atleast gave me an idea. Maybe I am just
> ignorant about how singularity works? I didn't know what -ti could
> possibly mean without first looking them up. Maybe I just need to add
> some additional arguments to singularity exec?
Well, is this invocation
singularity exec \
$(guix pack -f squashfs python python-numpy bash) \
python3
working for you?
> Arguments in the manual which look particularly interesting to me are:
>
> --contain
> --containall
> --bind=/path/to/shared/file/system/location
> --no-home
> --workdir
This depends on what you would like to achieve. ;-)
> If you or anyone else have have any tips on how to best mimic the
> behavior of the analogous `guix shell' command with an `singularity
> exec' call I would use if guix was available, I am all ears.
Basically,
guix shell -C -m manifest.scm -- something
is more or less similar to,
singularity exec $(guix pack -f squashfs -m manifest.scm) something
But since Guix is not running on the cluster, you need to build the pack
on your machine running Guix – this will produce a self contained
archive, say using the format Squashfs (Singularity).
Hope that helps,
simon
prev parent reply other threads:[~2023-02-16 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 0:25 guix pack isolation Kyle Andrews
2023-02-14 18:46 ` Simon Tournier
2023-02-15 23:56 ` Kyle Andrews
2023-02-16 9:44 ` Simon Tournier [this message]
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=86cz6ac5cv.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=kyle@posteo.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).