Fatal error - running typescript app in Gramine GSC (npx) #1468
Answered
by
dimakuv
tiagorvmartins
asked this question in
Q&A
-
|
I am trying to run a very simple typescript app using npx but I am missing something, because the container stops with a fatal error. The manifest: The Dockerfile of the image being graminized: Commands used to build and sign: Below you can find the debug log of the stopped container. |
Beta Was this translation helpful? Give feedback.
Answered by
dimakuv
Jul 21, 2023
Replies: 1 comment 8 replies
-
|
I think I know the problem. Here it is: https://github.com/nodejs/node/blob/e7c397739ff935e8b0f54505a4e37ca711e69d94/deps/v8/src/base/platform/platform-posix.cc#L571-L575 Gramine' support for gramine/libos/src/bookkeep/libos_vma.c Line 1307 in 24319e4 This may be possible to hack around, but needs thinking... |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
To be honest, I am absolutely not familiar with the Node.JS and Typescript worlds. Maybe someone else could comment on this. To me, if looks like the common codebase of Node.JS has this problem... So I would assume that many Node.JS apps would fail... |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dimakuv to give an update, I converted the small typescript app to standard javascript in order to be ran by the node binary itself, and I found the same error you mentioned on the logs "madvise..", I believe it might the app itself, however I wonder if this example have the same issue https://github.com/gramineproject/examples/tree/master/nodejs My last attempt will be running that example, if everything goes fine, then I will change the code being used to my app, and test again using the example structure, this means no GSC Will get back to you, thank you |
Beta Was this translation helpful? Give feedback.
-
|
@dimakuv Update: Using the example repo and swapping helloworld.js with my app worked without any problems. Any clues on what I am doing wrong? |
Beta Was this translation helpful? Give feedback.
-
|
@tiagorvmartins I think you have different versions on your bare metal system (where Gramine succeeds) and inside Docker (where GSC fails). Can you check the Node.JS versions? |
Beta Was this translation helpful? Give feedback.
Answer selected by
tiagorvmartins
-
|
You are right, was using node binary 20.04 from the docker image instead of the one being used on the example sample (which used node 18.17 - the one on the machine itself). Problem solved ;) |
Beta Was this translation helpful? Give feedback.
-
|
@tiagorvmartins But problem is not really solved, but rather circumvented? If I understand correctly, the Node.JS v20.04 is broken under Gramine? (Whereas the older v18.17 works fine.) Is this correct? This would mean that Gramine needs to fix this particular problem, to make newer Node.JS working again. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I believe so @dimakuv, at least using node v20.04 I wasn't able to run my app. For entire confirmation what could be done is: installing node v20.04 on the machine itself and run the nodejs example sample from the examples gramine repo which contains simple helloworld console log in javascript. If this fails to run in gramine then we would be sure that problem relies on the node version itself when used with gramine, and not related with any app-specific code. Thank you! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@tiagorvmartins I think you have different versions on your bare metal system (where Gramine succeeds) and inside Docker (where GSC fails). Can you check the Node.JS versions?