Read the statement by Michael Teeuw here.
Cannot find module 'node-fetch' error with MMM-SoccerLiveScore
-
@codac then you didnt do the npm install in the correct module folder
and I assume you have to restart MM of the container to pick up the change -
root@04492d039b9f:/opt/magic_mirror/modules# cd MMM-SoccerLiveScore root@04492d039b9f:/opt/magic_mirror/modules/MMM-SoccerLiveScore# npm install node -fetch@2 up to date, audited 1 package in 1s found 0 vulnerabilities
How would I restart MM of the container?
pm2 is not set up.DISPLAY=:0 npm restart
…results in
> magicmirror@2.26.0 restart > npm stop --if-present && npm start > magicmirror@2.26.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js sh: 1: ./node_modules/.bin/electron: not found
-
@codac seen this happening more
in the container again
in the MagicMirror folder donpm install electron@27.2.0
-
@sdetweil
sorry for the hussle, but this seems to never end :anguished_face:after running
npm install electron@27.2.0
I tried to restart MM:
root@04492d039b9f:/opt/magic_mirror# DISPLAY=:0 npm restart > magicmirror@2.26.0 restart > npm stop --if-present && npm start > magicmirror@2.26.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js /opt/magic_mirror/node_modules/electron/dist/electron: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory
-
@codac yeh, seems that electron needs something from the container
do you know which container you are using?@karsten13 can u look at this
-
he must restart the container, this cannot be done from inside the container
so how was the container started? With
docker compose
oderdocker run ...
or? -
@karsten13 this
libgobject-2.0.so.0: cannot open shared object file: No such file or directory
will be fixed by container restart ?
-
I don’t now, the old electron process is still running
but we now nothing, how he started, in server only or with electron, which architecture, which host os, which hardware …
-
docker run
-
@sdetweil
This error only comes up when trying to restart MM inside the docker.
When restarting the docker, this error wont show up.