-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add support for arm64 on Linux #70
Comments
Which part of the ruby standalone are you interested in using? eg. the pact broker CLI, or the pact mock service/verifier. |
The ideal would be to have support to everything. |
The reason I ask is that the mock service and verifier are being replaced in each of the languages by a shared rust lib, so the "pact" commands in the standalone are pretty much legacy now. The pact-broker CLI commands have their own docker image. So it would help to know which parts of the standalone you're using, and for which language, because they'll need to be solved differently. |
It would be nice to at least be able to install Right now it's impossible to build a Docker image for any JavaScript application that uses
|
Travelling Ruby (what we use to package up the pact-ruby-standalone) is not being maintained any more, and is unlikely to ever be supported for M1. We're transitioning all the pact clients away from that and onto a shared rust library. The Rust library will be supported on M1 (but I don't know the timing on this). @mefellows and @TimothyJones might be able to add more information about this. I believe theres is a work around for the M1 issue however, as one of my colleagues is currently running the standalone on her M1. Try searching in the pact-js issues or asking in the #pact-js Slack channel. |
To run on node, you need to install it and run through Rosetta mode. |
For "everything" support it will unlikely be possible via the standalone, as the maintainer of that library has basically stated they will no longer be adding major updates. You could install the bits you need via rubygems or we could add arm support to the docker image (ruby itself can run on arm, so we'd just need to build an arm image). |
For those trying to build an image which includes pact on M1 Macs you specify the platform;
Solution is outline in detail here. |
Are we going to fix this issue, we are looking at this as urgent. Any help on this would be appreciable. |
Does the docker command that Tim linked above not work for you? What problems are you encountering? |
☝🏾 to that linked issue, I have got some very alpha arm64 osx and linux standalone packages you can trial https://github.com/YOU54F/pact-ruby-standalone/releases/tag/v3.1.2.2-alpha Note these aren't official builds so your mileage might vary and you shouldn't rely on them at the moment until we get some feedback Direct Download
Script here https://github.com/YOU54F/pact-ruby-standalone/blob/ruby_3.2.2_upgrade/install.sh HomeBrewhttps://github.com/you54f/homebrew-pact-ruby-standalone
FlatPakhttps://github.com/YOU54F/flatpak Scoop
https://github.com/YOU54F/scoop ## Choco
|
@SanjayaKumarSahoo what functionality are you requiring from the standalone package, that isn't available in other means? Same question for @maatthc - you say support everything - we will do that in Rust, where it suits, but we need to know what in particular is of use to you currently in the Ruby package, that isn't in the Rust package. Most of the functionality is available via other means, cross compiled for additional platforms (and rust makes it very easy to support new ones), the ruby packaging system in general doesn't lend itself well for the platforms/archs we now want to cover (there are lots more people working on the rust cross compiling that those working on packaging ruby apps standalone, x-platform) |
You want it? You got it! See https://github.com/pact-foundation/pact-ruby-standalone/releases/tag/v2.0.0 Now, just don't break it 😂 |
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):Software versions
Expected behaviour
Would be nice to have support to aarch64 as Amazon and Oracle Cloud have good offers for instances on this platform.
Actual behaviour
Available executable are not compatible with ARM.
Steps to reproduce
Try to run any of the released packages on Arm-based AWS Graviton2 processors on EC2.
Relevent log files
Please ensure you set logging to
DEBUG
and attach any relevant log files here (or link from a gist).The text was updated successfully, but these errors were encountered: