-
Notifications
You must be signed in to change notification settings - Fork 6
Ruby 2.7.5 #4
Comments
I just rebuilt the gem with the latest images and published v0.5.3.2. Can you try that out? |
unfortunately still same issue:
|
It seems a arch-related issue! Dockerfile:
Sh:
|
Oh! So your image is amd64? I've never published a gem with multiple architecture needs before. Do you have thoughts on that? Should I publish a |
Actually, to make it work I had to force my image to be based on amd64 version. On my M1, by default it uses the arm64 base image. Considering that using arm64 is an option on Lambda, would be great to have the option. |
It could. I'd like to consider this project deprecated given we now have Lambda Containers and can easily install the needed development/build and/or runtime dependencies as needed in each of our containers. I recently provided an example in the new Lamby Cookiecutter work which is based on Ruby 3.1 official Debian images. Details here: |
The gem doesn't seem to work on ruby 2.7.5
Bundle installs all the gems, but when I try to require the gem, I get this error:
It worked with ruby 2.7.4, but AWS updated the base image with ruby 2.7.5
Here is my Dockerfile:
The file is there
but it doesn't seem to be a dynamic exec
The text was updated successfully, but these errors were encountered: