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
Use ruby:3.1.4-bullseye #7442
Use ruby:3.1.4-bullseye #7442
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this 🙏
Some of the smoke tests are failing but those are due to reasons outside of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch!
Maybe in the future we can keep it simple and base the whole image off of the official Ruby one to avoid this.
…-bullseye-image Use ruby:3.1.4-bullseye
Use ruby:3.1.4-bullseye Commit taken from dependabot#7442 The docker ruby images have updated which have a different set of packages installed. This locks to a specific image.
Use ruby:3.1.4-bullseye Commit taken from dependabot#7442 The docker ruby images have updated which have a different set of packages installed. This locks to a specific image.
Fixes #7438
The official Docker Ruby image tags used to default to Debian Bullseye, but now that there's a new release of Debian, the Docker image points to the new release.
This breaks things when we try to build or run Core:
This PR points our Ruby tag to the older Debian Bullseye image that we expect.