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 building the ipp_base image, the process fails on conflicting pins error:
Step 7/10 : RUN conda install --quiet --yes -c conda-forge ipywidgets jupyter jupyterlab ipython pillow paraview=5.8.0=py37ha369aaf_8 nodejs numpy matplotlib scipy
---> Running in 0d084e3e746c
Channels:
- conda-forge
- defaults
Platform: linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... warning libmamba Added empty dependency for problem type SOLVER_RULE_UPDATE
failed
LibMambaUnsatisfiableError: Encountered problems while solving:
- package paraview-5.8.0-py37ha369aaf_8 requires python >=3.7,<3.8.0a0, but none of the providers can be installed
Could not solve for environment specs
The following packages are incompatible
├─ paraview ==5.8.0 py37ha369aaf_8 is installable and it requires
│ └─ python >=3.7,<3.8.0a0 , which can be installed;
└─ pin-1 is not installable because it requires
└─ python 3.12.* , which conflicts with any installable versions previously reported.
Pins seem to be involved in the conflict. Currently pinned specs:
- python 3.12.* (labeled as 'pin-1')
The command '/bin/bash -c conda install --quiet --yes -c conda-forge ipywidgets jupyter jupyterlab ipython pillow paraview=5.8.0=py37ha369aaf_8 nodejs numpy matplotlib scipy' returned a non-zero code: 1
Does anyone have a suggestion how to fix the problem? What is the pin-1 here? I haven't found a reference to it in the repository and neither pin to python 3.12.*.
The text was updated successfully, but these errors were encountered:
When building the
ipp_base
image, the process fails on conflicting pins error:Does anyone have a suggestion how to fix the problem? What is the pin-1 here? I haven't found a reference to it in the repository and neither pin to python 3.12.*.
The text was updated successfully, but these errors were encountered: