Skip to content

Mixed ownership / permissions in /opt/conda #354

Description

@jameslamb

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.

ci-imgs/ci-conda.Dockerfile

Lines 246 to 259 in 59359a0

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'
)

ci-imgs/ci-conda.Dockerfile

Lines 228 to 229 in 59359a0

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions