all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Todor Kondić" <tk.code@protonmail.com>
To: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Guix and openmpi in a container environment
Date: Sun, 19 Jan 2020 10:25:14 +0000	[thread overview]
Message-ID: <eDyHjoEBk5ElBlodOM64zKfzyODszswvmo9giS35CnMv1MVYPF_Vj7W9GQ50GHdoTm0hBqi_QpiZ-h6qG6qa-jgdNOPDlrOlgWfPj_We25M=@protonmail.com> (raw)

I am getting mpirun errors when trying to execute a simple

mpirun -np 1 program

(where program is e.g. 'ls') command in a container environment.

The error is usually:

All nodes which are allocated for this job are already filled.

which makes no sense, as I am trying this on my workstation (single socket, four cores -- your off-the-shelf i5 cpu) and no scheduling system enabled.


I set up the container with this command:

guix environment -C -N --ad-hoc -m default.scm

where default.scm:

(use-modules (guix packages))
(specifications->manifest
 `(;; Utilities
   "less"
   "bash"
   "make"
   "openssh"
   "guile"
   "nano"
   "glibc-locales"
   "gcc-toolchain@7.4.0"
   "gfortran-toolchain@7.4.0"
   "python"
   "openmpi"
   "fftw"
   "fftw-openmpi"
   ,@(map (lambda (x) (package-name x)) %base-packages)))



Simply installing openmpi (guix package -i openmpi) in my usual Guix profile just works out of the box. So, there has to be some quirk where the openmpi container installation is blind to some settings within the usual environment.

             reply	other threads:[~2020-01-19 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 10:25 Todor Kondić [this message]
2020-01-27 10:54 ` Guix and openmpi in a container environment Todor Kondić
2020-01-27 12:48   ` Todor Kondić
2020-02-12 14:10 ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='eDyHjoEBk5ElBlodOM64zKfzyODszswvmo9giS35CnMv1MVYPF_Vj7W9GQ50GHdoTm0hBqi_QpiZ-h6qG6qa-jgdNOPDlrOlgWfPj_We25M=@protonmail.com' \
    --to=tk.code@protonmail.com \
    --cc=help-guix@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.