[BUG] builds failing: cannot import name 'views' from 'conda.notices'

[jameslamb]

Describe the bug

Many builds here are failing like this:

#15 47.88     Traceback (most recent call last):
#15 47.88       File "/opt/conda/lib/python3.13/site-packages/conda/exception_handler.py", line 30, in __call__
#15 47.88       File "/opt/conda/lib/python3.13/site-packages/conda/cli/main.py", line 53, in main_subshell
#15 47.88       File "/opt/conda/lib/python3.13/site-packages/conda/cli/conda_argparse.py", line 190, in do_call
#15 47.88       File "/opt/conda/lib/python3.13/site-packages/conda/notices/core.py", line 132, in wrapper
#15 47.88       File "/opt/conda/lib/python3.13/site-packages/conda/notices/core.py", line 82, in display_notices
#15 47.88     ImportError: cannot import name 'views' from 'conda.notices' (/opt/conda/lib/python3.13/site-packages/conda/notices/__init__.py)

example: https://github.com/rapidsai/docker/actions/runs/26052679561/job/76593003851#step:9:4428

Steps/Code to reproduce bug

N/A

Expected behavior

Builds should succeed.

Environment details (please complete the following information):

Latest main and release/26.06 (f6d23d2)

Additional context

N/A

[jameslamb]

This looks like a possible culprit: conda/conda#15879

These jobs are getting conda==26.5.0, which was released 3 days ago: https://github.com/conda/conda/releases/tag/26.5.0

That PR isn't in the release notes, but its commit is in the tag: conda/conda@b4eb1b6

[jameslamb]

It's notable that we're seeing a path like File "/opt/conda/lib/python3.13/site-packages/conda/exception_handler.py", line 30, in __call__ (with Python 3.13) into a job that's supposed to be building for Python 3.11.

And that all the Python 3.13 jobs (and ONLY the python 3.13 jobs) are succeeding in CI: https://github.com/rapidsai/docker/actions/runs/26052679561/job/76593003851#step:9:4428

I haven't yet been able to reproduce this locally with the condaforge/miniforge image + conda commands alone... I'm afraid the root cause might be related to this copying we do:

docker/Dockerfile

Line 99 in f6d23d2

COPY --from=miniforge-upstream --chown=root:conda --chmod=770 /opt/conda /opt/conda

Example of what I tried locally, which does not fail on the same line as those failing CI jobs:

docker run \
    --rm \
    -it condaforge/miniforge3:26.1.0-0 \
    bash

export PATH="/opt/conda/bin:${PATH}"

conda update --all -y -n base
conda clean -aiptfy

conda info
conda config --show-sources
conda list --show-channel-urls

conda install -y -n base 'python>=3.11,<3.12.0a0=*_cpython'
conda update --all -y -n base

[jameslamb]

Ok have a local reproducer!

This is the line that's failing:

docker/Dockerfile

Line 113 in f6d23d2

/tmp/build-scripts/configure-conda-base-environment

Comment that out, then run a local build of the miniforge-cuda target.

export CPU_ARCH=amd64
export CUDA_VER=13.0.2 
export LINUX_DISTRO=ubuntu
export LINUX_DISTRO_VER=24.04
export LINUX_VER=ubuntu24.04
export PYTHON_VER=3.14
export RAPIDS_VER=26.06

docker build $(ci/compute-build-args.sh) \
    --target=miniforge-cuda \
    -t rapidsai/base:local \
    -f Dockerfile \
    context/

The inside that image, run the failing install line.

$ docker run --rm -it rapidsai/base:local bash
$ conda install -y -n base "python>=3.11,<3.12.0a0=*_cpython"
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<                                                                                                            
                                                                                                                                                                        
    Traceback (most recent call last):                                                                                                                                  
      File "/opt/conda/lib/python3.13/site-packages/conda/exception_handler.py", line 30, in __call__                                                                   
      File "/opt/conda/lib/python3.13/site-packages/conda/cli/main.py", line 53, in main_subshell                                                                       
      File "/opt/conda/lib/python3.13/site-packages/conda/cli/conda_argparse.py", line 190, in do_call                                                                  
      File "/opt/conda/lib/python3.13/site-packages/conda/notices/core.py", line 132, in wrapper                                                                        
      File "/opt/conda/lib/python3.13/site-packages/conda/notices/core.py", line 82, in display_notices                                                                 
    ImportError: cannot import name 'views' from 'conda.notices' (/opt/conda/lib/python3.13/site-packages/conda/notices/__init__.py)                                    
                                                                                                                                                                        
`$ /opt/conda/bin/conda install -y -n base python>=3.11,<3.12.0a0=*_cpython`                                                                                            
                                                                                                                                                                        
  environment variables:                                                                                                                                                
                 CIO_TEST=<not set>                                                                                                                                     
             CONDA_PREFIX=/opt/conda                                                                                                                                    
               CONDA_ROOT=/opt/conda                                                                                                                                    
           CURL_CA_BUNDLE=<not set>                                                                                                                                     
          LD_LIBRARY_PATH=/usr/local/nvidia/lib:/usr/local/nvidia/lib64:/usr/local/cuda/lib64                                                                           
               LD_PRELOAD=<not set>                                                                                                                                     
                     PATH=/opt/conda/bin:/usr/local/nvidia/bin:/usr/local/cuda/bin:/usr/local/sb
                          in:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
           PYTHON_VERSION=3.14
       REQUESTS_CA_BUNDLE=<not set>
            SSL_CERT_FILE=<not set>

     active environment : base
    active env location : /opt/conda
       user config file : /root/.condarc
 populated config files : /opt/conda/.condarc
          conda version : 26.5.0
    conda-build version : not installed
         python version : 3.13.12.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=skylake
                          __conda=26.5.0=0
                          __glibc=2.39=0
                          __linux=6.17.0=0
                          __unix=0=0
       base environment : /opt/conda  (writable)
      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
          package cache : /opt/conda/pkgs
                          /root/.conda/pkgs
       envs directories : /opt/conda/envs
                          /root/.conda/envs
    temporary directory : /tmp
               platform : linux-64
             user-agent : conda/26.5.0 requests/2.34.2 CPython/3.13.12 Linux/6.17.0-23-generic ubuntu/24.04.4 glibc/2.39 solver/libmamba conda-libmamba-solver/26.4.2 libmambapy/2.6.1
                UID:GID : 0:1001
             netrc file : None
           offline mode : False


An unexpected error has occurred. Conda has prepared the above report.
If you suspect this error is being caused by a malfunctioning plugin,
consider using the --no-plugins option to turn off plugins.

Example: conda --no-plugins install <package>

Alternatively, you can set the CONDA_NO_PLUGINS environment variable on
the command line to run the command without plugins enabled.

Example: CONDA_NO_PLUGINS=true conda install <package>

I did try following the suggestion to run without plugins, that failed with a different error 😫

$ conda --no-plugins  install -y -n base "python>=3.11,<3.12.0a0=*_cpython"
Retrieving notices: done

CondaValueError: You have chosen a non-default solver backend (libmamba) but it was not recognized. Choose one of: clas

Also noting... the import it's complaining about works fine by itself.

$ python -c "from conda.notices import views; print(views.__file__)"
/opt/conda/lib/python3.11/site-packages/conda/notices/views.py

[jameslamb]

I might see an issue here. Before that conda install to downgrade Python:

$ ls /opt/conda/lib | grep -i python
libpython3.13.so
libpython3.13.so.1.0
libpython3.so
python3.13

After the failed conda install:

$ ls /opt/conda/lib | grep -i python
libpython3.11.so
libpython3.11.so.1.0
libpython3.so
python3.1
python3.11

That python3.1/ directory is weird and suspicious. nevermind, guess they're expected: conda-forge/python-feedstock#611

[gforsyth]

Also seeing the same failure mode in ci-imgs: https://github.com/rapidsai/ci-imgs/actions/runs/26057524971/job/76609236506?pr=408#step:9:6848

[jakirkham]

Does running conda notices reproduce it?

If so, are we able to reproduce this with a fresh Miniforge install?

[gforsyth]

Doesn't seem to occur on a fresh miniforge image:

󰕈 gforsyth  ~   v3.13.11   16:24 
🐚 docker pull condaforge/miniforge3
Using default tag: latest
latest: Pulling from condaforge/miniforge3
689b91d88a0f: Pull complete
c6d71295c85f: Pull complete
Digest: sha256:e005c6b132774b4093b96af586fe46a2464efec691ebbeefd1b710d291f8a67e
Status: Downloaded newer image for condaforge/miniforge3:latest
docker.io/condaforge/miniforge3:latest

󰕈 gforsyth  ~   v3.13.11   16:24 
🐚 docker run -it condaforge/miniforge3:latest /bin/bash
(base) root@851751091ecf:/# conda notices
Retrieving notices: done
(base) root@851751091ecf:/#

[jameslamb]

I haven't been able to reproduce it in a fresh miniforge image: #878 (comment)

I really think our pattern of copying /opt/conda across builds is related to this. That's caused issues before (though struggling to find links right now).

I think updating Python before this copy:

docker/Dockerfile

Line 99 in f6d23d2

COPY --from=miniforge-upstream --chown=root:conda --chmod=770 /opt/conda /opt/conda

Might help. Trying that locally.

[jameslamb]

Think I might see the issue.

conda/conda/notices/__init__.py looks like this:

from .core import notices

(code link)

That's importing a function called notices, not the content of the notices/ module.

The offending line in conda/notices/core.py has a deferred import inside a function call, like this:

def display_notices(channel_notice_set: ChannelNoticeResultSet) -> None:
    """Prints the channel notices to std out."""
    from . import cache, views

(code link)

When that relative import runs, it's getting its view of the module from that __init__.py, and that doesn't include views.

Now I'm not sure at all why we haven't been able to reproduce this yet, will investigate that.

[gforsyth]

I can reproduce it for the ci-imgs failure running this in the root of the ci-imgs repo:

docker buildx build --build-arg GH_CLI_VER=2.90.0 --build-arg CODECOV_VER=11.2.8 --build-arg YQ_VER=4.53.2 --
build-arg AWS_CLI_VER=2.28.1 --build-arg MINIFORGE_VER=26.1.0-0 --build-arg SCCACHE_VER=0.14.0-rapids.13 --build-
arg RAPIDS_VERSION_MAJOR_MINOR=26.08 --build-arg CUDA_VER=12.2.2 --build-arg LINUX_VER=rockylinux8 --build-arg PY
THON_VER=3.12 --build-arg CPU_ARCH=amd64 --build-arg REAL_ARCH=x86_64 --build-arg MANYLINUX_VER=manylinux_2_28 --
build-arg CONDA_ARCH=linux64 --file ci-conda.Dockerfile context/

So far, looks like maybe bumping to miniforge3:26.1.1-2 helps? spoke too soon

The ci-imgs builds for ci-conda.Dockerfile that use Python 3.13 are passing -- for those ones there is no version downgrade (or upgrade): https://github.com/rapidsai/ci-imgs/actions/runs/26057524971/job/76609236426?pr=408

Yeah, if we have PYTHON_VER set to 3.11, 3.12, or 3.14 the job fails but it passes for 3.13.