conda-lock github action step failing due to github action setup-miniconda step

[scottyhq]

pangeo-docker-images/.github/workflows/CondaLock.yml

Line 51 in 2e6d92f

use-only-tar-bz2: true # IMPORTANT: This needs to be set for caching to work properly!

Apparently this is now an issue since conda-forge no longer creates .tar.gz for packages by default (conda-incubator/setup-miniconda#267)

@yuvipanda I discovered this for the following error trying to lock the forge image in #408

Encountered problems while solving:
  - nothing provides requested apache-beam-with-gcp 2.43.0

[weiji14]

Is a cache needed in the CondaLock.yml workflow? I see only conda-lock and mamba being listed in environment-condalock.yml. In the CryoCloud hub-image, we're using:

      # Install conda-lock library
      - name: Install conda-lock
        run: pip install conda-lock

and running conda-lock lock --mamba -k explicit -f environment.yml -p linux-64 still works.

[scottyhq]

Is a cache needed in the CondaLock.yml workflow?

I don't think the package cache is, so will remove it. If I understand the above linked issues conda-forge packages used to always include .tar.gz files by default, but going forward only .conda files are generated. So creating the environment or generating a lock can fail for newer packages. See for example the apache-beam-with-gcp which includes .tar.gzs for 2.42, but not 2.43:
https://anaconda.org/conda-forge/apache-beam-with-gcp/files