-
Notifications
You must be signed in to change notification settings - Fork 110
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
Gem::Exception OpenSSL is not available error in base image using Ruby 3.3.5 #205
Comments
I saw that new images went out for the ruby base. New SHA: Using the above SHA, this now allows for 2/3 of the CI jobs to pass and we no longer receive the original error of The CI jobs (originally all jobs failed):
If I run I've tried manually installing openssl with I'm able to confirm that by setting our ruby image explicitly to |
Using this sha: We are now getting the original error we had and all CI jobs fail. We are still getting around the issue by having our project pinned to |
We are still receiving the error ( |
Hey @LeviLong01 I was able to successfully import
For reference, this repository pertains to Lambda base images: Lambda Ruby Base Images. |
In our CI pipelines, we use the
public.ecr.aws/sam/build-ruby3.3:latest
image.A few days ago we started getting an error around OpenSSL causing our CI pipelines to fail for merge requests on our lambda project.
Full Error:
Gem::Exception OpenSSL is not available. Install OpenSSL and rebuild Ruby (preferred) or use non-HTTPS sources
The last successful build from this image was from the following SHA:
public.ecr.aws/sam/build-ruby3.3@sha256:94e72d39197164fc9e8cd0dd1c3ed04b62e18e6e5f9c26bd495ba9818807e4ae
Looking at that the ruby version used, it is ruby 3.3.4.
The failing builds are using the following SHA:
public.ecr.aws/sam/build-ruby3.3@sha256:7550bbd53ff6bd0eb0feb1fcb713bac18791526b4fc0c8fc33dea93e05861c10
Looking at the ruby version used, it is ruby 3.3.5.
I'm not sure exactly what would cause this issue, but appears to be when going to this version from AWS.
The text was updated successfully, but these errors were encountered: