ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Conda 23.3 made libmamba the default solver, cutting resolve times from minutes to seconds. Here's what changed, how to verify you're on it, and the channel-priority trap that breaks migrating workflows.
Learn how to diagnose and fix Conda's 'Solving environment' hangs and UnsatisfiableErrors using the libmamba solver, strict channel priority, and environment isolation.
Conda's channel_priority: strict setting in .condarc is documented to require all packages to originate from the highest-priority channel that provides them. When an environment.yml lists both defaults and conda-forge , and a package version exists in both channels with different build strings, the documentation does not specify whether strict priority manda
Goal Achieve identical environment resolution on local development machines, CI/CD pipelines, and container builds regardless of whether the Conda installation defaults to the classic solver or to libmamba. Constraints and uncertainty Conda 23.1 made libmamba the default solver, altering dependency resolution semantics (stricter conflict detection, different