-
Notifications
You must be signed in to change notification settings - Fork 932
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
Support for Apple M1 chips #2131
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/176633479 The labels on this github issue will be updated when the story is started. |
Hello @nirajhx, thanks for reporting this issue. Did you try running our macOS binary using |
Yeah, binary did work for me. Thanks 😊 |
Could someone re-open this issue? Albeit the workaround with |
@biolauri do you know if it is possible to cross-compile Golang binary for ARM on Linux? |
It looks like Apple Silicone is just a normal ARM we will look into this proposal as we start working on the improvement of our release process next couple of months. |
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/178307311 The labels on this github issue will be updated when the story is started. |
Great to hear @a-b! Yes, AFAIK, Apple Silicon is just normal ARM64 architecture. |
Binary did not work for me using the ZSH shell |
This guide is useful for installing Rosetta Shell and Homebrew and after the restart, you can run the command |
Technically now you can compile M1, check this |
Hi all, wondering if this is still on the radar? I unfortunately am not advanced enough to take the information above and compile the binary myself :) so am wondering if it's A. available somewhere or B. still in process or C. off the table? |
While M1 support is not entirely off the radar, I can't give you any specific timeline. |
Got it, thank you for the update. Is there an approach you would recommend for utilizing the CF CLI on ARM containers in the meantime? So far my best solution is running an AMD container on my M1-native docker desktop install, but the qemu runs everything so slowly (per Docker's known issues) that i'm better off using my local machine w/rosetta and praying i keep all my global programs/versions in sync. |
Any updates? |
@a-b about the infrastructure... do you need an Mac with M1 to run automate tests or just someone who can install and report if everything went well? |
By default installing via homebrew fails (workarounds exists, e.g. install x86-binary from tar.gz): Cloning into '/Volumes/Toolchain/homebrew/Library/Taps/cloudfoundry/homebrew-tap'... |
Temporary solution: docker run -it --mount src=`pwd`,target=/home/piper/app,type=bind ppiper/cf-cli:latest /bin/bash |
Thanks, it worked for me. |
same than @lokhmakov , but using https://gist.github.com/oarthursilva/e03d7766575a6b8d96a0c697aa1f6d4b#file-docke-compose-cf-yml run
|
Facing an issue while connecting on postgres by using I'm following the wiki https://help.sap.com/viewer/b3fe3621fa4a4ed28d7bbe3d6d88f036/Cloud/en-US/69036a6c0b3b4377a1ae6a1edd084988.html in order to establish connection with Postgres. I'm able to access the container and establish a ssh connection with Postgres (manually), the container exposes the port the flow: |
@oarthursilva, from your description it looks like the cause is not related to native support for Apple Silicon. |
cf-cli is a go binary and can be easily built on ARM. The only thing preventing it was this declaration in the homebrew formula. Fixes cloudfoundry#74, cloudfoundry/cli#2131.
any progress on this? |
Any progresses on this? I understand cf cli intel binary for Mac can work on M1 Mac once it's installed based on Rosetta technology. The problem is that users could not install easily cf cli on M1 Mac via Homebrew system unless applying the following kind of trick: The ideal resolution is to provide ARM64 binary for cf CLI. But, at least, should we work for something to enable M1 Mac users to install cf cli via homebrew easily without any tricks? |
I created a homebrew tap for this, which I will keep manually updated until the official release comes around: |
WOW. Thanks! The repository https://github.com/wanddynosios/homebrew-tap got a ⭐ dunno why this isnt yet added to official builld.. |
Our team just finished migrating our release process into GitHub Actions #2265 We discourage using 3rd party taps, to avoid confusion and support issues. |
When will this be resolved. |
@jeffreyaggrey It has been resolved for v8.4.0 and can now be installed via homebrew (see this commit) |
is it possible to support linux_arm as well when running docker on M1 Mac. Docker will use linux arm64 instead of amd64. Thus cf for linux_arm64 is needed. |
@rafikt1992 please create a separate GitHub Issue to track your proposal. Would you be open to helping with testing this? |
For anyone coming here thinking it still does not work with Homebrew: You'll need to explicitly tell brew to use v8: brew install cloudfoundry/tap/cf-cli@8 |
Update Brewfile with some changes for MacOS Monterey on ARM. * Cleanup some unused packages like blackbox, ansible, stellarium, keepassx * Replace cf-cli with cloudfoundry/tap/cf-cli@8, which includes ARM support - see cloudfoundry/cli#2131 * Install docker from the formula instead of the cask * zoomus is now renamed to zoom * The python formula now installs python3 so don't install both
Hi, I am trying to execute the command % brew install credhub-cli I am using Apple M2 system with Mac OS : 13.4.1 (ventura) Please help me how to fix this issue on the Apple M2 |
@sangareddynalla its been a while, but as far as I remember, the brew package has some architecture dependency. but not cli. So just install with x86 version of brew, and use it from your native terminals |
Please provide details on the following items. Failure to do so may result in deletion of your feature request.
Not able to install on Apple MacBook with M1 chipset
What's the user value of this feature request?
Devs using the latest MacBook will be able to use cli
Who is the functionality for?
Devs using the latest M1 chip macbook
How often will this functionality be used by the user?
Always
Who else is affected by the change?
This should not affect the other versions
Is your feature request related to a problem? Please describe.
Trying to install CLI on my M1 chip MacBook, but the installation fails with following error:
Describe alternatives you've considered
I tried compiling the source code, but that also didn't workout. Got following error:
The text was updated successfully, but these errors were encountered: