From: Sebastian Gibb via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Unable to run host commands with singularity in a `guix pack -f squashfs` conainer
Date: Thu, 15 Jul 2021 19:39:48 +0000 (UTC) [thread overview]
Message-ID: <9ad5e61c-c0b3-415c-a19a-c3a894662766@sebastiangibb.de> (raw)
In-Reply-To: <162577254731.334077.10363679869099326954@x1>
Hi,
> The HPC uses Cent OS 8.1. It offers slurm 20.02.5 for job scheduling and
> singularity 3.4.2 for virtualisation/own software bundles.
> ...
> I could workaround the `ssh` problem by putting `openssh-sans-x` into the
> `guix pack` command and binding `/etc/group`, `/etc/passwd` and `/var/run`
> to my singularity container. But if I include `slurm` I always got an error
> for `sinfo`/`sbatch`:
> "slurm_partitions: Zero Bytes were transmitted or received"
> (maybe I need to bind some more pathes to singularity?)
I got it working by putting a slurm with the same major.minor version into the
singularity container.
Best wishes,
Sebastian
prev parent reply other threads:[~2021-07-15 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 19:29 Unable to run host commands with singularity in a `guix pack -f squashfs` conainer Sebastian Gibb via
2021-07-15 19:39 ` Sebastian Gibb via [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=9ad5e61c-c0b3-415c-a19a-c3a894662766@sebastiangibb.de \
--to=help-guix@gnu.org \
--cc=mail@sebastiangibb.de \
/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).