The following argument was not expected: --no-builds

We use it here:

@JohanMabille I created an upstream issue: mamba-org/mamba#3492

UPDATE: I fixed this one by not using --json and using --no-build flag, which works for both v1 and v2

Also: bash: line 1: conda: command not found

It seems that conda executable is now missing

I don't know if this is expected or not and the best way to fix this.

Fixed this issue with the output of mamba list --full-name (it now works in mamba v2, but the output format has slightly changed, not a bug).
Also fixed an issue with mamba env export (reported to the upstream, but we no longer need it to be fixed).
And I did it in a way that works with both mamba v1 and v2.

The only remaining issue is with the missing conda executable.
We use it like this in 2 places: eval "$(conda shell.bash hook)".
As far as I see, the conda package is no longer installed when installing mamba, and that's why executable is missing.
And if I try to install it manually, it downgrades mamba to v1.

We can try to switch to eval "$(mamba shell hook)", but this is not something I would really like to do:

1. I assume many of our users have conda install/activate commands in the images based on our images. Not having a conda executable will break them.
2. We have some documentation ourselves suggesting using conda - this will also silently break.
3. mamba shell hook doesn't exist in mamba v1, as far as I understand. This means we will make it difficult for users who fork our repo to stay with mamba v1 if they are not ready to upgrade yet.

So, we should probably wait till we can install both conda and mamba v2 simultaneously.

Hi Ayaz,

Regarding failing update due to conda, you might want to track mamba-org/mamba#3503.