-
Notifications
You must be signed in to change notification settings - Fork 26
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
Can't start on A1 Oracle instances because of outdated Node.js version #98
Comments
Hi, the reason for using this specific version of Node.js is that I want to keep it in sync with the version that the official UISP images use. The issue you linked says that Node.js 12 and 13 doesn't work, but 11 and 14 does. This image currently uses Node.js 16 for everything except Netflow, which still uses Node.js 12, like Ubiquiti does. I'd assume that Node.js 16 works fine on A1 Oracle if it was fixed in Node.js 14? Also, Netflow shouldn't prevent the start of UISP, so it will most likely work without it, or do you explicitly need Netflow? Last time I tried, Netflow did not run on newer Node.js versions (#60) Could you please clarify if the image doesn't run at all or if only Netflow doesn't work? If it doesn't run at all, which Node.js version is needed for it to run on A1 Oracle? |
Hi! Interesting, but Node.js 12 is mentioned here as supported version for ARM, maybe the issue is finally fixed in latest versions? |
nope, latest node-12 (12.22.12) doesn't work too, attempting to build with 14.21.3 now |
with 14.21.3 as node-old I cannot see that error, container is started and seems to be working fine, will do some tests later |
Despite the support of aarch64/arm64 is mentioned at Docker Hub — prepared image doesn't start on A1 Oracle CPUs because of this issue.
As following comment states — that bug is already fixed in latest Node.js image. Could you please rebuild your image with newer Node version?
The text was updated successfully, but these errors were encountered: