Repository navigation
Node issue with satellite installer #129
Replies: 1 comment 4 replies
|
Ah, thank you for this bug report. How frustrating! I am deliberately shipping Satellite with Node v18 to combat this very thing. In my experience Node v18 is widely compatible with older OSes, and as soon as Node v20 came out everything started breaking on AL2 and similar. Sigh! Yeah, I see the problem now. I just spun up an AL2 box. I guess I was wrong about the version -- it's Node v18 where everything broke on older OSes: Dang! I suppose I should go all the way back to Node v16 and ship that with Satellite, but... at a certain point it becomes a security problem, because Node v16 is EOL and won't receive any security updates anymore. It's frozen in time. Ugh, what a hairy problem.
You're absolutely right, but honestly I have little choice. I'm kind of stuck between a rock and a hard place. Very few people would allow Satellite to shell out to The other option is a single-file self-contained binary, but alas, the popular vercel pkg library was abandoned recently, and Node.js' own built-in self-executable thing is still experimental (and it'll only support much newer OSes anyway). So I was left with the only option I could think of, which was to ship a static Node binary with Satellite, and keep everything "contained" in the Hmmm, I'll keep thinking about this... |

Uh oh!
There was an error while loading. Please reload this page.
I didn't see this in other threads, so I wanted to drop a note about my experience installing satellite servers. Mostly, it worked flawlessly. I am running the UI on an amazon linux 2023 server, and pasted a the curl command in an amazon linux 2 server. The script failed when it tried to execute the node binary that was retrieved because AL2's glibc isn't compatible. I replaced the /opt/xyops/satellite/bin/node binary with the local system one (nodejs 16 or 18) and then manually pasted the rest of the script and the install completed and the server showed up. Hopefully the node swap doesn't cause any problems. I don't know if there was a compatible one that should have been identified instead or if my OS is just too old (EOL on AL2 is June 2026). I doubt a static node is a good idea lol. Just wanted to give you some feedback. So far, I absolutely love xyops. It's so clean and easy. I am staging a migration from a very built-out cronicle - so far so good!
All reactions