Test spack build using external dependencies

[BenjaminRodenberg]

Related to #86

Todo

• get test working
• Make sure that permissions are reasonable, i.e. have a non-privileged user for testing to be able to reproduce error described in Phase install_lib fails using Spack if system's Python is used #86

[BenjaminRodenberg]

I tried building the spack base image, but ran into trouble with building boost, when building locally via docker build -t external-deps -f spack/ci-spack-pyprecice-external-deps-2004.dockerfile .:

==> Installing boost-1.77.0-ih2n3iejl2kufyybakahhq4tottejwer
==> No binary for boost-1.77.0-ih2n3iejl2kufyybakahhq4tottejwer found: installing from source
==> Fetching https://boostorg.jfrog.io/artifactory/main/release/1.77.0/source/boost_1_77_0.tar.bz2
==> Ran patch() for boost
==> boost: Executing phase: 'install'
==> Error: ProcessError: Command exited with status 1:
    './bootstrap.sh' '--prefix=/spack/opt/spack/linux-ubuntu20.04-x86_64/gcc-8.4.0/boost-1.77.0-ih2n3iejl2kufyybakahhq4tottejwer' '--with-toolset=gcc' '--with-libraries=regex,wave,test,thread,exception,system,date_time,graph,locale,chrono,log,serialization,filesystem,iostreams,random,timer,atomic,program_options,math' '--without-icu'
See build log for details:
  /tmp/root/spack-stage/spack-stage-boost-1.77.0-ih2n3iejl2kufyybakahhq4tottejwer/spack-build-out.txt

This needs some further investigation.

[BenjaminRodenberg]

Currently, the spack package is not widely used. Testing how the package behaves with dependencies from the base system is probably useful but also increases cost for testing and general complexity. We can keep this PR lying around or close it. Any opinion @fsimonis ?

I took care of updating the most obvious parts and added some comments at the relevant places.

[BenjaminRodenberg]

That's the relevant line in this dockerfile compared to ci-spack-pyprecice-deps-2404.dockerfile