You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Start container with docker compose up
Server (please complete the following information):
Etherpad version: 2.2.5
OS: default Docker container with Alpine Linux v3.20
Node.js version (node --version): v22.9.0
npm version (npm --version): 10.8.3
Is the server free of plugins: yes
The text was updated successfully, but these errors were encountered:
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.
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: