Description
See these:
It seems that the files created by later mamba install calls have different permissions from those copied in from the upstream condaforge/miniforge image.
|
PACKAGES_TO_INSTALL=( |
|
'anaconda-client>=1.13.1' |
|
'ca-certificates>=2026.1.4' |
|
'certifi>=2026.1.4' |
|
'conda-build>=25.11.1' |
|
'conda-package-handling>=2.4.0' |
|
'dunamai>=1.25.0' |
|
'git>=2.52.0' |
|
'jq>=1.8.1' |
|
'packaging>=25.0' |
|
"python>=${PYTHON_VERSION},<${PYTHON_UPPER_BOUND}=*_${PYTHON_ABI_TAG}" |
|
'rapids-dependency-file-generator==1.*' |
|
'rattler-build>=0.55.0' |
|
) |
|
rapids-mamba-retry install -y \ |
|
gettext |
That hasn't yet caused any issues in RAPIDS CI, but it could in the future. And the details at rapidsai/docker#762 (comment) suggest some ways it could cause issues for interactive use (which is common: https://docs.rapids.ai/resources/reproducing-ci/)
I'm also unsure if those differing permissions are intentional or just a mistake.
That should be investigated and fixed if there's something to fix here.
Description
See these:
It seems that the files created by later
mamba installcalls have different permissions from those copied in from the upstreamcondaforge/miniforgeimage.ci-imgs/ci-conda.Dockerfile
Lines 246 to 259 in 59359a0
ci-imgs/ci-conda.Dockerfile
Lines 228 to 229 in 59359a0
That hasn't yet caused any issues in RAPIDS CI, but it could in the future. And the details at rapidsai/docker#762 (comment) suggest some ways it could cause issues for interactive use (which is common: https://docs.rapids.ai/resources/reproducing-ci/)
I'm also unsure if those differing permissions are intentional or just a mistake.
That should be investigated and fixed if there's something to fix here.