Skip to content
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.

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

Bad CPU type in executable in m1 mac #279

Open
wkjung opened this issue Feb 21, 2023 · 2 comments
Open

Bad CPU type in executable in m1 mac #279

wkjung opened this issue Feb 21, 2023 · 2 comments

Comments

@wkjung
Copy link

wkjung commented Feb 21, 2023

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?

@jaimergp
Copy link
Member

Does it work if you use installer-url directly?

@goanpeca
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants