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
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
There seems to be an issue with the activate.sh script failing in case the user doesn't have permissions to modify the symlink.
For example, in the following Dockerfile, if the environment is activated by root, then all subsequent non-root user activations fail with
ln: failed to create symbolic link '/opt/conda/share/gdb/auto-load//opt/conda/lib/*.py': Permission denied
FROM mambaorg/micromamba:git-3208378
RUN micromamba install -y -n base -c conda-forge libarrow
ARG MAMBA_DOCKERFILE_ACTIVATE=1
USER root
RUN echo "Environment containing libarrow activated as root"USER $MAMBA_USER
RUN echo "Activate as user without root permission"
I'm not sure how to best mitigate this, but one simple idea would be to not recreate the symlink if it already exists and points to the correct location.
Installed packages
See Dockerfile
Environment info
See Dockerfile
The text was updated successfully, but these errors were encountered:
Solution to issue cannot be found in the documentation.
Issue
There seems to be an issue with the
activate.sh
script failing in case the user doesn't have permissions to modify the symlink.For example, in the following Dockerfile, if the environment is activated by
root
, then all subsequent non-root user activations fail withI'm not sure how to best mitigate this, but one simple idea would be to not recreate the symlink if it already exists and points to the correct location.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: