Skip to content
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

Segmentation fault in ruby:3.2.2-alpine3.18 docker image #540

Closed
imamdg opened this issue Aug 11, 2023 · 2 comments
Closed

Segmentation fault in ruby:3.2.2-alpine3.18 docker image #540

imamdg opened this issue Aug 11, 2023 · 2 comments

Comments

@imamdg
Copy link

imamdg commented Aug 11, 2023

While trying to deploy an app with base image ruby:3.2.2-alpine3.18, I was facing the following error. It was working fine with docker compose in Macbook m2 pro.

/usr/local/bundle/gems/pg-1.4.6/lib/pg/connection.rb:627: [BUG] Segmentation fault at 0x00000001000001b7

ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux-musl]

-- Control frame information -----------------------------------------------
c:0045 p:---- s:0270 e:000269 CFUNC :connect_poll
c:0044 p:0358 s:0266 e:000265 METHOD /usr/local/bundle/gems/pg-1.4.6/lib/pg/connection.rb:627
c:0043 p:0265 s:0253 e:000252 METHOD /usr/local/bundle/gems/pg-1.4.6/lib/pg/connection.rb:761
c:0042 p:0007 s:0242 e:000241 METHOD /usr/local/bundle/gems/pg-1.4.6/lib/pg/connection.rb:696

After a series of trial and error, we managed to resolve the issue by downgrading the Ruby Docker image to ruby:3.2.2-alpine3.16. ruby:3.2.2-alpine3.17 also has the same problem.

@drdrsh
Copy link
Contributor

drdrsh commented Aug 30, 2023

It will probably help if you can provide a Minimal reproducible example that demonstrates the issue

@jcdennen
Copy link

there seem to be a crop of seg faults recently, I wonder if they're related. have you tried the fix proposed in this issue? #538 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants