After update, chrome-sandbox needs root and mode 4655?

karsten13

thx, so you are on the develop branch with electron 6.x

sdetweil

@karsten13 and old node and npm

karsten13

yes, saw that, but my tests were run with

node@pi4:/opt/magic_mirror$ node -v
v13.5.0
node@pi4:/opt/magic_mirror$ npm -v
6.13.4

sdetweil

@karsten13 u are ok, he is downlevel…

installer is still only checking node 10 minimum… should I change it?

karsten13

thats your decision, this problem seems unrelated to the node/npm version, but so old stuff can cause other problems, so may you should warn at least …

sdetweil

@karsten13 if installer is used, i upgrade to latest 10.x, and latest npm… don’t warn

karsten13

o.k., so your question was about using a newer node version than 10? Maybe the latest lts version, I’m not sure, think this is 12.

sdetweil

@karsten13 both 10 and 12 are lts, 12 just started, 10 entering maint in April, 12 enters maint in october

Release Status Codename Initial Release Active LTS Start Maintenance LTS Start End-of-life
v10 Active LTS Dubnium 2018-04-24 2018-10-30 2020-04-01 2021-04-30
v12 Active LTS Erbium 2019-04-23 2019-10-21 2020-10-21 2022-04-30

Richard238

Would it be advisable then, regardless of the chrome-sandbox issue, to update NODE and NPM on my MM?

If so how, and to which version of each?

karsten13

I think they all work, you’re using 10, the official docker image uses 12 and I’m using 13 in my images …