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

install_asm fails while running make apply #352

Closed
martham93 opened this issue Feb 23, 2022 · 1 comment
Closed

install_asm fails while running make apply #352

martham93 opened this issue Feb 23, 2022 · 1 comment
Assignees

Comments

@martham93
Copy link

Hello!

I'm trying to setup kubeflow on GCP and am following the instructions here/ the instructions from this repo'skubeflow directory readme.

However the make apply step fails on the install_asm step with the following error. I'm running the setup commands on a Mac OS (arm64). I'm working with Kubeflow v1.5.0-rc.0 blueprints. Any suggestions for how to get install_asm to run?

install_asm: Setting up necessary files...
install_asm: Creating temp directory...
install_asm:
install_asm: *****************************
install_asm: No output folder was specified with --output_dir|-D, so configuration and
install_asm: binaries will be stored in the following directory.
install_asm: /var/folders/h3/mwwjd1fn1jd39w6qdl24j52r0000gn/T/tmp.4fczZeEe
install_asm: *****************************
install_asm:
install_asm: Using asm_kubeconfig as the kubeconfig...
install_asm: Fetching/writing GCP credentials to kubeconfig file...
install_asm: Verifying connectivity (10s)...
install_asm: kubeconfig set to asm_kubeconfig
install_asm: context set to gke_pachama-labs_us-central1-c_kubeflow
install_asm: Checking installation tool dependencies...
install_asm: [ERROR]: Installation is only supported on x86_64.
make[1]: *** [install-asm] Error 2
@zijianjoy
Copy link
Collaborator

Hello @martham93 , currently we don't support running install_asm on MacOS. It is the limitation of ASM. What you can do is to create a VM which is Linux to continue the deployment process. Another way is to try upgrading your bash to 5.1 as suggested in #330. But keep in mind that you might encounter some other issues after this one.

@gkcalat gkcalat closed this as completed Mar 31, 2023
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