Local macOS Conda Environment vs Linux Production Container: Package Version Divergence

Goal: Recreate an environment defined in an environment.yml file on a macOS developer workstation inside a Linux-based production container with identical package versions and builds.

Uncertainty arises because conda resolves platform-specific package builds at install time, channel priority settings can shift package sources, transitive dependencies are re‑solved in the target environment, and some pinned versions may lack Linux builds or require different system libraries such as glibc or CUDA.

Which configuration options (channel priority, subdir, explicit pinning) most reliably reproduce the macOS package set on Linux? How can one verify Linux availability of a package version before building the container? What is the impact of using the libmamba solver versus the classic solver on cross‑platform reproducibility?