Closed riazXrazor closed 1 year ago
Do you still get SegFault when you use debian based node images?
Seems related to https://github.com/sodium-friends/sodium-native/issues/160
Yeah ok, alpine uses musl and not glibc. Actually would recommend for better performance anyway to avoid alpine.
I am closing this issue because it is an upstream issue.
Please be patient on for the new release of sodium-native
, the fix is merged but not released yet.
For the current workaround. You can either
sodium-native@3.3.0
by explicit install and npm dedupe
node:lts
ok got it, thanks guys for some much needed help , i hv been stuck on this for a while now
Just pin it for now, I believe a lot of developer keen on using alpine
.
They may face the exact same issue.
sodium-native
has been fixed, please update to https://github.com/fastify/fastify-secure-session/releases/tag/v6.0.0.
Prerequisites
Fastify version
4.0.0
Plugin version
5.3.0
Node.js version
18.x.x
Operating system
Linux
Operating system version (i.e. 20.04, 11.3, 10)
node:lts-alpine
Description
Hi, i have been trying to implement azure ad login using the package
@fastify/passport
withpassport-azure-ad
which requires the use of@fastify/secure-session
for session management but when ever i run my project in docker and try the azure ad login route i getSegmentation Fault
. i m usingnode-segfault-handler
to catch the error.Below is my dockerfile
BTW when i run without docker just on my pc , it works , no errors
Steps to Reproduce
visiting below route gives Segmentation Fault error and crashes the api server when the project ran in docker
Expected Behavior
ideally ot should redirect to microsoft for azure login if i visit this route below in screenshot