Skip to content

Conda environment creation script uses proprietary Anaconda channels #582

@jrandall

Description

@jrandall

Some of the example scripts download Miniconda and use its defaults, which includes the use of the default channels which since March 2024 have required a paid license for any organizations of over 200 employees (see: https://redresscompliance.com/anaconda-licensing-changes-explained/).

Many organizations have chosen to move away from using the default channels and are now using environments created using only content from community channels, such as conda-forge (see https://conda-forge.org/docs/user/transitioning_from_defaults/).

Some of the scripts in this repo include a step that downloads Miniconda3 from anaconda.com and then installs and uses it with the default configuration, which includes the default channels.

For example: https://github.com/aws-samples/awsome-distributed-training/blob/4740c3fddfc2d7eb0e5df47dd2603188a08aa700/3.test_cases/10.FSDP/0.create_conda_env.sh

As an alternative, it may be simpler to switch to using micromamba in the examples which is somewhat simpler as the micromamba binary does not require a base environment to run, and also uses the conda-forge channel in the default configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions