The cache user directory is non-writable (owned by root).

[hadim]

Comment:

The cache user directory (/home/conda/.cache) is non-writable (owned by root).

I noticed this while building locally from a feedstock bash .scripts/run_docker_build.sh using rattler-build and got the below error:

 ╰─────────────────── (took 8 seconds)
 × error Error building package: Failed to resolve dependencies: failed to acquire a lock on the repodata cache
Error:   × Failed to resolve dependencies: failed to acquire a lock on the repodata cache
  ├─▶ failed to acquire a lock on the repodata cache
  ├─▶ failed to open: /home/conda/.cache/rattler/cache/repodata/3018e552.lock
  ╰─▶ Permission denied (os error 13)

You can check the permissions of the cache folder with:

$ docker run --rm -ti quay.io/condaforge/linux-anvil-cos7-x86_64:latest ls -la /home/conda/.cache 
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
total 12
drwxr-xr-x 3 root  root  4096 Oct  1 22:06 .
drwx------ 3 conda conda 4096 Oct  1 22:06 ..
drwxr-xr-x 2 root  root  4096 Oct  1 22:06 rosetta

The cache folder in the image is empty except for one empty folder called rosetta/.

I am not sure from where this root permission is coming from and what is this rosetta/ folder as well.

[hadim]

Maybe worth noting, I am running the docker build from a macOS Silicon laptop.

[hadim]

Ok so it seems to be macOS specific....

On a Linux machine:

docker run --rm -ti quay.io/condaforge/linux-anvil-cos7-x86_64:latest ls -la /home/conda/
total 24
drwx------ 2 conda conda 4096 Oct  1 22:20 .
drwxr-xr-x 1 root  root  4096 Oct  1 22:20 ..
-rw-r--r-- 1 conda conda   18 Nov 24  2021 .bash_logout
-rw-r--r-- 1 conda conda  193 Nov 24  2021 .bash_profile
-rw-r--r-- 1 conda conda  231 Nov 24  2021 .bashrc
-rw-r--r-- 1 conda conda   75 Oct  1 22:20 .condarc

It's not a c-f bug, so I will close here.

[hadim]

For the record: docker/for-mac#7440

[hadim]

Again for the record as a quick workaround:

export CONDA_FORGE_DOCKER_RUN_ARGS="-e XDG_CACHE_HOME=/tmp/.cache"
bash .scripts/run_docker_build.sh

[jakirkham]

Interesting am on a Mac, but am using Rancher Desktop. This is what I see

$ docker run --rm -ti quay.io/condaforge/linux-anvil-cos7-x86_64:latest ls -la /home/conda/
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
total 24
drwx------ 2 conda conda 4096 Oct  1 22:35 .
drwxr-xr-x 1 root  root  4096 Oct  1 22:35 ..
-rw-r--r-- 1 conda conda   18 Nov 24  2021 .bash_logout
-rw-r--r-- 1 conda conda  193 Nov 24  2021 .bash_profile
-rw-r--r-- 1 conda conda  231 Nov 24  2021 .bashrc
-rw-r--r-- 1 conda conda   75 Oct  1 22:35 .condarc

So agree it looks like a Docker Desktop specific bug

[hadim]

Switching to Rancher now :-)

[hadim]

It's actually more a docker emulation engine question than docker versus rancher.

When I enable the Rosetta emulation (in order to run linux-64 build) then I get the same issue as above.

[hadim]

xref with

• When building locally with build-locally.py, getting git error fatal: detected dubious ownership in repository at '/home/conda/staged-recipes' staged-recipes#26779
• Permissions issue when running build-locally.py: Permission denied: '/home/conda/.cache/conda' staged-recipes#26781

[jakirkham]

Interesting when using the aarch64 container on my Mac, don't see the issue either

$ docker run --rm -ti quay.io/condaforge/linux-anvil-aarch64 ls -la /home/conda/
total 24
drwx------ 2 conda conda 4096 Oct  2 00:19 .
drwxr-xr-x 1 root  root  4096 Oct  2 00:19 ..
-rw-r--r-- 1 conda conda   18 Nov 24  2021 .bash_logout
-rw-r--r-- 1 conda conda  193 Nov 24  2021 .bash_profile
-rw-r--r-- 1 conda conda  231 Nov 24  2021 .bashrc
-rw-r--r-- 1 conda conda   75 Oct  2 00:19 .condarc

So could be some corner case. Not really sure

[hadim]

I think it only happens when the host is on a different arch. This is when Rosetta is used.