From: Kyle Andrews <kyle@posteo.net>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix pack isolation
Date: Wed, 15 Feb 2023 23:56:33 +0000 [thread overview]
Message-ID: <87cz6ao2n0.fsf@posteo.net> (raw)
In-Reply-To: <874jroyti6.fsf@gmail.com>
Simon Tournier <zimon.toutoune@gmail.com> writes:
> About squashfs (Singularity container), you can try:
>
> guix pack -f squashfs python python-numpy bash-minimal -S /bin=bin
>
> which will produce a compressed squashfs that you then import with
> Singularity.
This is pretty much what I had tried minus the `-S /bin=bin' part which
I don't understand. Thankfully, reading the manual informs me that:
```
‘guix pack -f squashfs’ always implies ‘-S /bin=bin’
```
So, atleast I don't have to understand it yet.
> 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.
> $ 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?
Arguments in the manual which look particularly interesting to me are:
--contain
--containall
--bind=/path/to/shared/file/system/location
--no-home
--workdir
=>
https://docs.sylabs.io/guides/3.1/user-guide/cli/singularity_exec.html
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.
Thanks,
Kyle
next prev parent reply other threads:[~2023-02-16 0:50 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 [this message]
2023-02-16 9:44 ` Simon Tournier
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=87cz6ao2n0.fsf@posteo.net \
--to=kyle@posteo.net \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).