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
When running Dockerfile.centos7, the docker image gets to step 5/5 and produces an error which indicates that the path to conda is not valid. This means the path either does not exist or the path is not accessible (I do not have admin privileges on the computer I am running this on).
The docker command:
docker build -t tbillah/fsl-6.0.6-centos7 -f Dockerfile.centos7 .
The error:
=> ERROR [5/5] RUN /root/fsl-5.0.11-centos7/fslpython/bin/conda install -y -n fslpython -c conda-forge deprecation==1.* 0.4s
[5/5] RUN /root/fsl-5.0.11-centos7/fslpython/bin/conda install -y -n fslpython -c conda-forge deprecation==1.*:
0.347 /bin/sh: /root/fsl-5.0.11-centos7/fslpython/bin/conda: No such file or directory
On second thought, I think conda is in the right place. You are making mistake with directory name. Is /root/fsl-5.0.11-centos7 still the directory where you installed 6.0.5? Carefully examine this, I think you can figure this out. You are close!
When running Dockerfile.centos7, the docker image gets to step 5/5 and produces an error which indicates that the path to conda is not valid. This means the path either does not exist or the path is not accessible (I do not have admin privileges on the computer I am running this on).
The docker command:
docker build -t tbillah/fsl-6.0.6-centos7 -f Dockerfile.centos7 .
The error:
=> ERROR [5/5] RUN /root/fsl-5.0.11-centos7/fslpython/bin/conda install -y -n fslpython -c conda-forge deprecation==1.* 0.4s
Dockerfile.centos7:32
30 |
31 | # apply patch
32 | >>> RUN $FSLDIR/fslpython/bin/conda install -y -n fslpython -c conda-forge deprecation==1.*
33 |
34 |
ERROR: failed to solve: process "/bin/sh -c $FSLDIR/fslpython/bin/conda install -y -n fslpython -c conda-forge deprecation==1.*" did not complete successfully: exit code: 127
The text was updated successfully, but these errors were encountered: