-
Notifications
You must be signed in to change notification settings - Fork 13
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
Problem with Docker Node-Red #132
Comments
That looks like a segmentation fault coming from NodeJS itself - not seen that before. In theory, that should never happen, no matter how messed up the JavaScript is. I suspect it's something to do with serialport, which node-red-contrib-rfxcom depends on, as I have seen a lot of (different) issues arising with the serialport/Docker combination recently. It might be worth checking for NodeJS bug reports, too |
serial node do similar segmentation fault. It cause a specific version of serial port pre-compiled binary. This commit will try to fix it. it help you a bit? |
node-serialport v11 should include the fix, you will need to kick/poke upstream dependencies to pick it up |
Hello @maxwellhadley What do you think, it possible to fix this problem? |
Version 2.13.0 now published to npm uses serialport 11.x.x, to retain compatibility with NodeJS v14. This should fix your issue |
Hello there,
I try to migrate my local Node-RED install to Docker, but if this node is active, the Node-RED can not start...
Seems the problem is connect this (the error message is same):
serialport/node-serialport#2438
The text was updated successfully, but these errors were encountered: