-
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
Running the standalone package inside of a ruby container fails #56
Comments
Thanks. This is a known issue and is documented somewhere (we've had similar issues with other environment variables). It probably makes sense to explicitly unset this variable in the entry scripts in this repository. |
Looks like #50 fixed this, but for batch files. |
Hey @johnduhart Just came across this issue during the upgrade to ruby 3.2.2 as I wanted to use it as a builder image, as it was quicker than builder ruby from source. pact-ruby-standalone/.cirrus.yml Lines 13 to 27 in b8c1020
Applying the change to the |
Will get it updated, and out :) |
I would not use the standalone inside of a container. it will be super slow. Much better to actually install ruby and the native gem. |
I've encountered something similar to #17, where running the standalone package inside of a container is failing. After spending a few hours troubleshooting I've managed to narrow down the problem. Example dockerfile to reproduce:
I'm currently getting the following error:
The cause of this appears to be the
BUNDLE_APP_CONFIG
set on theruby
container. Adding the follow to the Dockerfile fixes the problem:I don't know if this is something that needs to be fixed upstream or in this package, but at the very least I wanted to just document this issue for anyone else that may encounter this.
The text was updated successfully, but these errors were encountered: