-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Update broke Lambda Runners #420
Comments
The code in your post uses You can technically add the component yourself with the following, but it's best to use the right base image builder.
There is also an issue where we expect you to use Finally it looks like we're using node14 as the base image for this. That should definitely be updated. The last two can be addressed with:
|
Node 14.x is very EOL. Node 16.x should also be removed, but I tried upgrading to Node 18.x and got: ``` ERROR Cannot get required symbol EVP_rc2_cbc from libssl ERROR ./config.sh: line 81: 204 Aborted (core dumped) ./bin/Runner.Listener configure "$@" ERROR Invoke Error {"errorType":"Error","errorMessage":"Runner failed with exit code 134","stack":["Error: Runner failed with exit code 134"," at ChildProcess.<anonymous> (/var/task/runner.js:24:16)"," at ChildProcess.emit (node:events:514:28)"," at ChildProcess._handle.onexit (node:internal/child_process:291:12)"]} ``` See #420
This got it! Possibly relevant to you: node16 is now apparently EOL. Ugh... |
Just upgraded for the first time in half a year; now the Lambda runner is dying instantly with zero visibility, almost like the entrypoint is wrong. Help?
My code:
The text was updated successfully, but these errors were encountered: