@jbedo do you also disable the sandbox?

I suppose what I'm seeing is nix trying to set up mount namespaces for the builds, but idk:

Singularity> nix-shell -p gh
error: executing shell '/nix/store/k4j76vg58c6j90s8l46kx3843vysx732-bash-interactive-5.2-p15/bin/bash': No such file or directory
Singularity> nix shell nixpkgs#gh
error: setting up a private mount namespace: Operation not permitted
Singularity>

In reply to @ss:someonex.net

@jbedo do you also disable the sandbox?

I suppose what I'm seeing is nix trying to set up mount namespaces for the builds, but idk:

Singularity> nix-shell -p gh
error: executing shell '/nix/store/k4j76vg58c6j90s8l46kx3843vysx732-bash-interactive-5.2-p15/bin/bash': No such file or directory
Singularity> nix shell nixpkgs#gh
error: setting up a private mount namespace: Operation not permitted
Singularity>

In reply to @ryantalo:matrix.org
Ok, managed to get things building + running using the singularity method jbedo described; alas inode limits are killing me now. It seems that nix build nixpkgs#hello is essentially evaluating every nix package for some reason; why would /nix/store/tmp-1759374-1/x/pkgs/development/python-modules/qimage2ndarray be getting built for a simple c binary otherwise...

In reply to @twesterhout:matrix.org
Hello, has anybody managed to run MPI-aware applications via nix-portable or Nixie on an HPC cluster where Nix isn't installed? Single-node executables work fine, but I'm struggling to do anything with multi-node stuff. Currently trying to go through Singularity with pkgs.singularity-tools, but no luck so far. So if anybody has an example, that'd very much appreciated.