setup-miniconda icon indicating copy to clipboard operation
setup-miniconda copied to clipboard

Bad CPU type in executable in m1 mac

Open wkjung opened this issue 2 years ago • 2 comments

Doesn't it support self-hosted action runner on m1 Mac?

If I use setup-miniconda on my self-hosted runner (m1 mac, arm64 runner), it detects the machine architecture as x64 and fails to be installed.

      uses: conda-incubator/setup-miniconda@v2
      with:
        environment-file: conda/${{ matrix.CONDA_ENV_NAME }}.yml
        miniconda-version: "latest"
        activate-environment: ${{ matrix.CONDA_ENV_NAME }}
# output
Run conda-incubator/setup-miniconda@v2
  with:
    environment-file: conda/dev.yml
    miniconda-version: latest
    activate-environment: dev
    auto-activate-base: true
    auto-update-conda: false
    remove-profiles: true
    architecture: x64                                           <------------------------------ WHY?
    clean-patched-environment-file: true
    run-post: true

which ends up with:

Running installer...
  /bin/bash /Users/wk/actions-runner/_work/_temp/fa40e615-78bd-43ef-aad1-28b4c1a4f3c1.sh -f -b -p /Users/runner/miniconda3
  PREFIX=/Users/runner/miniconda3
  Unpacking payload ...
  Warning: /Users/wk/actions-runner/_work/_temp/fa40e615-78bd-43ef-aad1-28b4c1a4f3c1.sh: 
line 351: /Users/runner/miniconda3/conda.exe: Bad CPU type in executable

Even if I change the architecture to 'ARM64' it refuses to install:

Run conda-incubator/setup-miniconda@v2
Gathering Inputs...
Creating bootstrap condarc file in /Users/wk/.condarc...
Ensuring installer...
Error: Invalid miniconda version!

Must be among Miniconda3-latest-Linux-aarch64.sh,Miniconda3-py39_23.1.0-1-Linux-aarch64.sh,Miniconda3-py38_23.1.0-1-Linux-aarch64.sh,Miniconda3-py37_23.1.0-1-Linux-aarch64.sh,Miniconda3-py310_23.1.0-1-Linux-aarch64.sh,Miniconda3-py39_22.11.1-1-Linux-aarch64.sh,Miniconda3-py38_22.11.1-1-Linux-aarch64.sh,Miniconda3-py37_22.11.1-1-Linux-aarch64.sh,Miniconda3-py310_22.11.1-1-Linux-aarch64.sh,Miniconda3-py37_4.12.0-Linux-aarch64.sh,Miniconda3-py39_4.12.0-Linux-aarch64.sh,Miniconda3-py38_4.12.0-Linux-aarch64.sh,Miniconda3-py39_4.11.0-Linux-aarch64.sh,Miniconda3-py38_4.11.0-Linux-aarch64.sh,Miniconda3-py37_4.11.0-Linux-aarch64.sh,Miniconda3-py39_4.10.3-Linux-aarch64.sh,Miniconda3-py38_4.10.3-Linux-aarch64.sh,Miniconda3-py37_4.10.3-Linux-aarch64.sh,Miniconda3-py39_4.10.1-Linux-aarch64.sh,Miniconda3-py38_4.10.1-Linux-aarch64.sh,Miniconda3-py37_4.10.1-Linux-aarch64.sh,Miniconda3-py39_4.9.2-Linux-aarch64.sh,Miniconda3-py38_4.9.2-Linux-aarch64.sh,Miniconda3-py37_4.9.2-Linux-aarch64.sh

Can it be fixed?

wkjung avatar Feb 21 '23 07:02 wkjung

Does it work if you use installer-url directly?

jaimergp avatar Feb 22 '23 19:02 jaimergp

Could you try using version 2.1 or 2.0 and see if it works when you specify the architecture?

goanpeca avatar Feb 22 '23 19:02 goanpeca