-
Notifications
You must be signed in to change notification settings - Fork 93
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
Bundle install fails on CircleCI for mini_racer 0.6.0 #227
Comments
Just a sanity check: Are you running on alpine? |
It's not alpine based; the specific image/tag is ruby:3.0.3. |
This looks very similar to #218 |
This looks wrong then, @chrisalley. |
Seeing the same issue in GitHub Actions with the latest ruby/setup-ruby@v1.91.0 Error output
|
Same issue here with the ruby:3.0.2 image and mini_racer 0.5.0 |
Fwiw, we were finally able to resolve our issue by updating to latest bundler(2.3.5), as well as specifying platforms in Gemfile.lock. We are still running Ruby 2.7.x. |
If you are running into this issue, please make sure to update bundler (currently 2.3.5) and check if the platform you're running on is properly set in mini_racer 0.6.2 should work fine with Ruby 2.6.9, 2.7.5, 3.0.x and 3.1.0 (I tested a lot of those combination across x86 and aarch64 recently). Especially with the recent 0.6.2 the last issues with pre Ruby 3 environments got fixed. @mdh: awesome 👍 |
Solved with: bundle lock --add-platform aarch64-linux
bundle lock --add-platform x86_64-linux In Gemfile: gem 'mini_racer', '~> 0.6.2' In Dockerfile:
Only aarch64-linux was required as an added platform for CircleCI to succeed in installing mini_racer, but another gem (ransack) failed to install without x86_64-linux being added also. |
Great! I'm glad this worked out for you, @chrisalley!
Interesting 🤔 Didn't knew that CircleCI has an ARM offering :) |
Fixes issues installing libv8-node gem on CI. See: rubyjs/mini_racer#227
Fixes issues installing libv8-node gem on CI. See: rubyjs/mini_racer#227
Fixes issues installing libv8-node gem on CI. See: rubyjs/mini_racer#227
- update image https://discuss.circleci.com/t/legacy-convenience-image-deprecation/41034 - reset bundle cache with updated image - Set target bundle platforms rubyjs/mini_racer#227 (comment) - force circleCI to install latesr bundler version before building - update bundler `path` setting to resolved: [DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set path 'vendor/bundle'`, and stop using this flag
My point to this issue |
This fixes `bundle install` issues on ARM-based Macs (e.g. Macs with M1/M2 chips) by adding `arm64-darwin-21` to the platforms in Gemfile.lock. It also adds arm64 versions of a few gems, which were added automatically by bundler after fixing `bundle install` @see rubyjs/mini_racer#227 (comment)
This fixes `bundle install` issues on ARM-based Macs (e.g. Macs with M1/M2 chips) by adding `arm64-darwin-21` to the platforms in Gemfile.lock. It also adds arm64 versions of a few gems, which were added automatically by bundler after fixing `bundle install` @see rubyjs/mini_racer#227 (comment)
This fixes `bundle install` issues on ARM-based Macs (e.g. Macs with M1/M2 chips) by adding `arm64-darwin-21` to the platforms in Gemfile.lock. It also adds arm64 versions of a few gems, which were added automatically by bundler after fixing `bundle install` @see rubyjs/mini_racer#227 (comment)
This resolves an issue where native extensions wouldn't install when running `bundle install`. See rubyjs/mini_racer#227 (comment)
This resolves an issue where native extensions wouldn't install when running `bundle install`. See rubyjs/mini_racer#227 (comment)
This resolves an issue where native extensions wouldn't install when running `bundle install`. See rubyjs/mini_racer#227 (comment)
When running the bundle install command on CircleCI with mini_racer 0.6.0 in the Gemfile, the build fails. This did not occur with mini_racer 0.3.1. Output:
The text was updated successfully, but these errors were encountered: