Skip to content

Fix mamba version #6560

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lldelisle wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix mamba version #6560

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b8c3c5c
fix the name of executable for miniforge in the help
lldelisle Dec 10, 2025
0b3cd03
change the miniconda_version to match miniforge
lldelisle Dec 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions topics/admin/tutorials/ansible-galaxy/tutorial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -935,8 +935,8 @@ The configuration is quite simple thanks to the many sensible defaults that are
> `galaxy_force_checkout` | `true` | If we make any modifications to the Galaxy codebase, they will be removed. This way we know we're getting an unmodified Galaxy and no one has made any unexpected changes to the codebase.
> `galaxy_client_use_prebuilt` | `true` | We are going to use a prebuilt client to save some time during this tutorial, if you want you can set it to false later and see how galaxy starts building the client itself.
> `miniconda_prefix` | {% raw %}`"{{ galaxy_tool_dependency_dir }}/_conda"`{% endraw %} | We will manually install conda as well. Normally Galaxy will attempt to auto-install this, but since we will set up a production-ready instance with multiple handlers, there is the chance that they can become deadlocked.
> `miniconda_version` | `25.3` | Install a specific miniconda version, the latest one at the time of writing that was tested and working.
> `miniconda_distribution` | `miniforge` | Install a specific distribution of conda, see https://github.com/galaxyproject/ansible-miniconda for alternatives. This determines the default value for the `miniconda_executable` (`conda` for `miniforge`)
> `miniconda_version` | `2.4.0` | Install a specific miniconda version, the latest one at the time of writing that was tested and working.
Copy link
Copy Markdown
Contributor

@bernt-matthias bernt-matthias Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default conda distribution (confusingly called miniconda_distribution) seems to be miniforge. miniconda_version defaults to latest. Recent version numbers seem to be 25.x: https://github.com/conda-forge/miniforge/releases

Copy link
Copy Markdown
Collaborator Author

@lldelisle lldelisle Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. I agree that the default is miniforge.
  2. The associated executable is "mamba": https://github.com/galaxyproject/ansible-miniconda/blob/0b2ec2da7d143717b1f21baf15263adca1cc3fb7/defaults/main.yml#L161-L162
  3. For the version, I tried on my instance miniconda_version: 25.3 and I got an error.
    What the role is doing is:
    https://github.com/galaxyproject/ansible-miniconda/blob/0b2ec2da7d143717b1f21baf15263adca1cc3fb7/tasks/update.yml#L5-L8
    And the last version of mamba is 2.4.0

> `miniconda_distribution` | `miniforge` | Install a specific distribution of conda, see https://github.com/galaxyproject/ansible-miniconda for alternatives. This determines the default value for the `miniconda_executable` (`mamba` for `miniforge`)
Copy link
Copy Markdown
Contributor

@bernt-matthias bernt-matthias Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can note that miniforge is the default anyway.

Its conda: https://github.com/galaxyproject/ansible-miniconda/blob/0b2ec2da7d143717b1f21baf15263adca1cc3fb7/defaults/main.yml#L166

FYI: to my knowledge, nowadays there are only minor differences between conda and mamba anyway and according to @bgruening mamba is dead...

Copy link
Copy Markdown
Member

@bgruening bgruening Dec 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, mamba is dead, please use conda.

(The new cool kid in town is pixi, but I don't think we want to switch, we wait until conda has taken all the pixi advantages ;))

> `miniconda_channels` ` | `['conda-forge']` | Use the free and community-maintained `conda-forge` channel.
>
> > <tip-title>Different Galaxy Releases!</tip-title>
Expand Down Expand Up @@ -964,7 +964,7 @@ The configuration is quite simple thanks to the many sensible defaults that are
> +galaxy_client_use_prebuilt: true
> +galaxy_force_checkout: true
> +miniconda_prefix: "{{ galaxy_tool_dependency_dir }}/_conda"
> +miniconda_version: 25.3
> +miniconda_version: 2.4.0
> +miniconda_distribution: miniforge
> +miniconda_channels: ['conda-forge']
> {% endraw %}
Expand Down Expand Up @@ -997,7 +997,7 @@ The configuration is quite simple thanks to the many sensible defaults that are
> --- a/group_vars/galaxyservers.yml
> +++ b/group_vars/galaxyservers.yml
> @@ -13,3 +13,17 @@ miniconda_prefix: "{{ galaxy_tool_dependency_dir }}/_conda"
> miniconda_version: 25.3
> miniconda_version: 2.4.0
> miniconda_distribution: miniforge
> miniconda_channels: ['conda-forge']
> +
Expand Down Expand Up @@ -2281,7 +2281,7 @@ Finally, we have explicitly mapped the `local` class of tools to run in the `loc
> ```diff
> --- a/group_vars/galaxyservers.yml
> +++ b/group_vars/galaxyservers.yml
> @@ -14,6 +14,24 @@ miniconda_version: 25.3
> @@ -14,6 +14,24 @@ miniconda_version: 2.4.0
> miniconda_distribution: miniforge
> miniconda_channels: ['conda-forge']
>
Expand Down