-
Notifications
You must be signed in to change notification settings - Fork 136
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
/usr/local/bundle/gems/ffi-1.12.2/lib/ffi/library.rb:112: [BUG] Illegal instruction #47
Comments
Seems like the same error, although I'm not able to reproduce it. Can you try to add the workaround from sass/sassc-ruby#146?
Meanwhile I will also try to run it on Kali. |
ok, i will recreate the dockerfile locally and try the fix
|
I'm afraid it needs to be changed before build. I will try to debug it this
week
mar., 16 nov. 2021, 22:20 chrisvanzet ***@***.***> a scris:
… ok, i added the "LD_LIBRARY_PATH: /lib64" to docker-compose.yaml...still
the same issue
how can i change the failing gem (sassc) in a non starting container?
I tried
docker run -it dockername /bin/bash , but its still failing. Sorry for my
noobish docker questions, but i am new to this fancy docker stuff ;)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGQQ6UUMLGTFXDT5DGWWK7TUMK4I3ANCNFSM5IEVTCSA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
this is the working Dockerfile so far..
and the docker-compose.yml with some modifications..
Now the containers are starting up and also the pg "bad connection" error is gone. |
After admin login, i get this error.
maybe it's the uncommented line in the rails-app Dockerfile?
|
Yes, you need that line.
You have to add the workaround during build. You can also try to add this in the Dockerfile before entrypoint:
|
Hello,
i get this error when i start with "docker-compose up"
....
Could it be the same cause like here?
#sass/sassc-ruby#146
i use it on my Kali test machine
br
ckz666
The text was updated successfully, but these errors were encountered: