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
Considering all the issues about the expired certificates in pulled images (#189, #184, #193, #194...) and as it was suggested many times, I tried to build containers locally using docker compose build.
An issue occurs when trying to build websockify for the slurmdbd container, due to a numpy dependency without version in websockify that currently pulls numpy 2.2.2 that is not compatible with python39 used in the container. As already mentionned here, adding sed -i 's/numpy/numpy==1.26/' setup.py before
However, even if I managed to build all containers with this fix, I obtain a strange TLS connection error when trying to access Coldfront at https://localhost:2443/ :
Considering all the issues about the expired certificates in pulled images (#189, #184, #193, #194...) and as it was suggested many times, I tried to build containers locally using
docker compose build
.An issue occurs when trying to build
websockify
for theslurmdbd
container, due to anumpy
dependency without version inwebsockify
that currently pullsnumpy 2.2.2
that is not compatible withpython39
used in the container. As already mentionned here, addingsed -i 's/numpy/numpy==1.26/' setup.py
beforehpc-toolset-tutorial/slurm/install.sh
Line 53 in 6baa9a3
does the trick. Adding the package
python39-numpy
tohpc-toolset-tutorial/slurm/install.sh
Line 19 in 6baa9a3
might also work.
However, even if I managed to build all containers with this fix, I obtain a strange TLS connection error when trying to access Coldfront at https://localhost:2443/ :
or, with
curl
:Any help to understand the issue and manage to fix the build would be highly appreciated.
The text was updated successfully, but these errors were encountered: