"urls.txt": Permission denied

[allefeld]

I'm not sure whether this is a bug or just a misguided message, since the process completed fine.

I have installed conda via the apt repository (on Debian), i.e. the base environment is under /opt/conda and owned by root. Following the instructions, I installed mamba into the base environment, via sudo.

I then created an environment as regular user under my user's home, using mamba env create -f std.yml.

As mentioned the process completed fine (and brilliantly fast!) – I just noticed an error message in the first few lines of output:

$ mamba env create -f std.yml
error    libmamba Error opening for writing "/opt/conda/pkgs/urls.txt": Permission denied
pkgs/main/linux-64                                            No change
conda-forge/linux-64                                          No change
pkgs/main/noarch                                              No change
pkgs/r/linux-64                                               No change
pkgs/r/noarch                                                 No change
conda-forge/noarch                                   8.2MB @   3.4MB/s  2.5s
…

Is this important, and if yes, how would I fix it?

mamba info:

     active environment : None
            shell level : 0
       user config file : /home/ca/.condarc
 populated config files : /home/ca/.condarc
          conda version : 4.12.0
    conda-build version : not installed
         python version : 3.10.4.final.0
       virtual packages : __cuda=11.4=0
                          __linux=5.10.0=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /opt/conda  (read only)
      conda av data dir : /opt/conda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /opt/conda/pkgs
                          /home/ca/.conda/pkgs
       envs directories : /home/ca/.conda/envs
                          /opt/conda/envs
               platform : linux-64
             user-agent : conda/4.12.0 requests/2.27.1 CPython/3.10.4 Linux/5.10.0-14-amd64 debian/11 glibc/2.31
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

[wolfv]

Hi, thanks for the note. We should hide that message. It's mamba's way of figuring out to which directories it can write.

[jdblischak]

I also recently ran into this error message. I am installing mambaforge in a shared location on an HPC cluster. The idea is that many users can use the same mamba, but then their environments should be saved in ~/.conda/envs/. I agree that the message is harmless in that the environment is created and functional, but I am concerned that other users will be worried by the presence of an error message.

[ngam]

I also recently ran into this error message. I am installing mambaforge in a shared location on an HPC cluster. The idea is that many users can use the same mamba, but then their environments should be saved in ~/.conda/envs/. I agree that the message is harmless in that the environment is created and functional, but I am concerned that other users will be worried by the presence of an error message.

thanks @jdblischak for linking our conversation in conda-smithy. @wolfv, see there for a demo of how this turns out... conda-forge/conda-smithy#1623

[vsoch]

Just hit this error as well - it would definitely be beneficial to hide as it can be distracting from the underlying issue (a few lines down!)

[wolfv]

I think with the latest mamba / libmamba this should be improved :)

[jonashaag]

I assume this is fixed