HMNS section HDF5 install module only doesn't work when using Singularity

[akesandgren]

I.e. it doesn't work in the container setup.

eb HDF5-1.10.6-gompi-2020a.eb --robot --module-only
== temporary log file in case of crash /tmp/eb-aa7dv072/easybuild-yrxjqo2e.log
== found valid index for /scratch/ake/isc20/.local/easybuild/easyconfigs, so using it...
== resolving dependencies ...
== processing EasyBuild easyconfig /scratch/ake/isc20/.local/easybuild/easyconfigs/m/M4/M4-1.4.18.eb
== building and installing Core/M4/1.4.18...
  >> installation prefix: /easybuild/software/M4/1.4.18
== FAILED: Installation ended unsuccessfully (build directory: /scratch/ake/isc20/easybuild/build/M4/1.4.18/system-system): build failed (first 300 chars): Failed to create lock /easybuild/software/.locks/_easybuild_software_M4_1.4.18.lock: [Errno 30] Read-only file system: /easybuild/software/.locks/_easybuild_software_M4_1.4.18.lock (took 0 sec)

It fails first on the lock dir and once that has been redirected it fails to write the build log into the software dir
Failed to write to /easybuild/software/M4/1.4.18/easybuild/Core-M4-1.4.18-easybuild-devel:

[boegel]

The problem here is that /easybuild is read-only when you're running the container image with singularity run.

That's not the case when using Docker directly.

I don't think there's an easy fix for this...

I will clearly highlight this in the documentation that this demo/exercise won't work when using Singularity, that's the best I can do on short notice I think...

[boegel]

Got some feedback on this in the Singularity Slack:

in your %post section, you’ll probably want something like:
  find /easybuild -type d -exec chmod 1777 '{}' \;
  find /easybuild -type f -exec chmod 666 '{}' \;
  chmod 1777 /easybuild

Something worth trying in the Docker container, but not for the tutorial on June 23rd, not touching the container image anymore now since it works fine when using Docker in AWS...

[ocaisa]

Fixed with easybuilders/easybuild-framework#3659