You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if this is the right place to file this bug, or if it is even really a bug. However, we just ran into "No such variant 'noavx512' in package openblas" while attempting to create a gcc/openmpi based container image from the 1.8.0 release.
=> ERROR [builder 6/8] RUN cd /opt/spack-environment && spack env activate .&& spack install --fail-fast && spack gc -y 11.5s
------
> [builder 6/8] RUN cd /opt/spack-environment && spack env activate .&& spack install --fail-fast && spack gc -y:
10.20 ==> Error: cannot emit requirements forthe solver: No such variant 'noavx512'in package openblas
------
Dockerfile:521
--------------------
519 |
520 |# Install the software, remove unnecessary deps
521 | >>> RUN cd /opt/spack-environment && spack env activate .&& spack install --fail-fast && spack gc -y
522 |
523 |# Modifications to the environment that are necessary to run
--------------------
ERROR: failed to solve: process "docker-shell cd /opt/spack-environment && spack env activate . && spack install --fail-fast && spack gc -y" did not complete successfully: exit code: 3
make: *** [makefile:57: jcsda-spackstack] Error 1
To Reproduce
Here is a section of our makefile that clones the JCSDA Spack-stack repo and switches to the 1.8.0 release, before running spack containerize and building the image with docker build.
Is there an override/workaround we can employ so that our automated builds/CI won't fail without a manual edit or new Dockerfile. We are not well-versed in all of the available ways to configure a spack-stack, but not above using sed to modify the Dockerfile or yaml that is created.
The text was updated successfully, but these errors were encountered:
Description
I am not sure if this is the right place to file this bug, or if it is even really a bug. However, we just ran into "No such variant 'noavx512' in package openblas" while attempting to create a gcc/openmpi based container image from the 1.8.0 release.
To Reproduce
Here is a section of our makefile that clones the JCSDA Spack-stack repo and switches to the 1.8.0 release, before running
spack containerize
and building the image withdocker build
.Expected behavior
Completed docker build of a base 1.8.0 jcsda/spack-stack container image.
System:
The building is happening on an Ubuntu 20.04 machine.
Here is the full Dockerfile that is created:
Additional
Is there an override/workaround we can employ so that our automated builds/CI won't fail without a manual edit or new Dockerfile. We are not well-versed in all of the available ways to configure a spack-stack, but not above using
sed
to modify the Dockerfile or yaml that is created.The text was updated successfully, but these errors were encountered: