Switch CI Docker image from Miniconda to Miniforge#18858
Switch CI Docker image from Miniconda to Miniforge#18858
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18858
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below:
|
This PR needs a
|
…rate limits Replace Miniconda (which uses Anaconda's rate-limited default package repository) with Miniforge (which uses conda-forge). This resolves CI Docker image build failures caused by Anaconda ToS rate limits. This PR was authored with Claude. Agent-Logs-Url: https://github.com/pytorch/executorch/sessions/888dd7ec-0404-4883-b99c-d6b54cb95a05 Co-authored-by: kirklandsign <107070759+kirklandsign@users.noreply.github.com>
Summary
CI Docker image builds fail due to Anaconda package repository rate limits (
Your usage of the Anaconda package repository exceeds our rate limits).Switch from Miniconda to Miniforge, which uses conda-forge as its default channel and avoids Anaconda's default repository entirely. Miniforge is otherwise fully compatible.
.ci/docker/common/install_conda.sh: Download fromgithub.com/conda-forge/miniforge/releasesinstead ofrepo.anaconda.com/miniconda.ci/docker/build.sh:MINICONDA_VERSION=23.10.0-1→MINIFORGE_VERSION=24.11.3-0.ci/docker/ubuntu/Dockerfile:ARG MINICONDA_VERSION→ARG MINIFORGE_VERSIONTest plan
Verified both Miniforge download URLs (x86_64 and aarch64) resolve correctly. The rest of the conda environment setup (Python version selection, conda-env-ci.txt, pip dependencies, libstdc++ hack) is unchanged.