-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Docker-version nodejs too new #6687
Comments
Thanks for the issue. At some point I'll need to fork the dependency. This comes for whatever reason from a library that hasn't been updated. If you'd use the old NodeJS 18 runtime it won't display an error. But the big thing is everything is fine you can ignore the error for now. |
Attention: potentially dangerous link! |
Hi Same here.
In my case, it's a new and clean deployment using docker. So, is it fine to just ignore this warning? Thanks! |
Describe the bug
I'm currently trying to run etherpad from docker. It seems the nodejs version is too new, so etherpad is completely not functional. Starting the container (without deamonizing) I get the message "oidc-provider WARNING: Unsupported runtime. Use Node.js v18.x LTS, or a later LTS release." Checking the node version inside the container reveals v22.9.0. Opening its web interface, the admin page works, but the home page already doesn't. It's an almost blank page not showing much more than the field to set the pad name. And trying to open a pad from there doesn't result in anything happening.
To Reproduce
Steps to reproduce the behavior:
docker compose up
Server (please complete the following information):
node --version
): v22.9.0npm --version
): 10.8.3The text was updated successfully, but these errors were encountered: