Error running a container on multi-node about singularity HOT 5 CLOSED

Hello. The mount tmpfs->${path} portion of the error message likely indicates the problem here. The ${path} portion should instead be part of the path under which singularity was installed.

Please could you give the output of singularity buildcfg so we can see the configuration with which singularity was compiled?

from singularity.

Hello,

The ${path} is the full path where singularity is installed. I just replaced it with a variable.

Here is the the configuration:

$singularity buildcfg
PACKAGE_NAME=singularity
PACKAGE_VERSION=3.7.1
BUILDDIR=/home/rdah/singularity/builddir
PREFIX=/opt/cr/singularity/3.7.1
EXECPREFIX=/opt/cr/singularity/3.7.1
BINDIR=/opt/cr/singularity/3.7.1/bin
SBINDIR=/opt/cr/singularity/3.7.1/sbin
LIBEXECDIR=/opt/cr/singularity/3.7.1/libexec
DATAROOTDIR=/opt/cr/singularity/3.7.1/share
DATADIR=/opt/cr/singularity/3.7.1/share
SYSCONFDIR=/opt/cr/singularity/3.7.1/etc
SHAREDSTATEDIR=/opt/cr/singularity/3.7.1/com
LOCALSTATEDIR=/opt/cr/singularity/3.7.1/var
RUNSTATEDIR=/opt/cr/singularity/3.7.1/var/run
INCLUDEDIR=/opt/cr/singularity/3.7.1/include
DOCDIR=/opt/cr/singularity/3.7.1/share/doc/singularity
INFODIR=/opt/cr/singularity/3.7.1/share/info
LIBDIR=/opt/cr/singularity/3.7.1/lib
LOCALEDIR=/opt/cr/singularity/3.7.1/share/locale
MANDIR=/opt/cr/singularity/3.7.1/share/man
SINGULARITY_CONFDIR=/opt/cr/singularity/3.7.1/etc/singularity
SESSIONDIR=/opt/cr/singularity/3.7.1/var/singularity/mnt/session
PLUGIN_ROOTDIR=/opt/cr/singularity/3.7.1/libexec/singularity/plugin
SINGULARITY_CONF_FILE=/opt/cr/singularity/3.7.1/etc/singularity/singularity.conf
SINGULARITY_SUID_INSTALL=0

from singularity.

hello @dtrudg, do you have any idea on this issue please?

Thank you

from singularity.

Can you paste output of debug logs.. i.e. with singularity -d run ... as there isn't a lot to see here so far. The write unix @->@: write: broken pipe indicates that it hasn't been possible for communication of the mount instruction to be made across the socket that is used for that.

It's not something that has been seen before tbh. I cannot reproduce under the MPI environments I have available to me here. If you can verify it works under a different MPI stack, e.g. OpenMPI / MVAPICH etc. that'd be useful also.

from singularity.

Closing as there hasn't been further information provided. Please re-open if you are still having the problem and are able to provide additional diagnostic information.

from singularity.