Read the statement by Michael Teeuw here.
MagicMirror install on proxmox LXC Container?
-
o.k…next try to step and hope i can start the MM
look…
pi@MagicMirror-live:~$ curl -sL https://deb.nodesource.com/setup_18.x | sudo -E bash - [sudo] password for pi: ## Installing the NodeSource Node.js 18.x repo... ## Populating apt-get cache... + apt-get update Hit:1 https://deb.nodesource.com/node_16.x jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Get:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Fetched 224 kB in 2s (105 kB/s) Reading package lists... Done ## Confirming "jammy" is supported... + curl -sLf -o /dev/null 'https://deb.nodesource.com/node_18.x/dists/jammy/Release' ## Adding the NodeSource signing key to your keyring... + curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null ## Creating apt sources list file for the NodeSource Node.js 18.x repo... + echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x jammy main' > /etc/apt/sources.list.d/nodesource.list + echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x jammy main' >> /etc/apt/sources.list.d/nodesource.list ## Running `apt-get update` for you... + apt-get update Get:1 https://deb.nodesource.com/node_18.x jammy InRelease [4563 B] Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease Get:5 https://deb.nodesource.com/node_18.x jammy/main amd64 Packages [775 B] Fetched 5338 B in 2s (2387 B/s) Reading package lists... Done ## Run `sudo apt-get install -y nodejs` to install Node.js 18.x and npm ## You may also need development tools to build native addons: sudo apt-get install gcc g++ make ## To install the Yarn package manager, run: curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt-get update && sudo apt-get install yarn pi@MagicMirror-live:~$ sudo apt-get update && sudo apt-get install yarn Hit:1 https://deb.nodesource.com/node_18.x jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'cmdtest' instead of 'yarn' The following additional packages will be installed: python3-cliapp python3-importlib-metadata python3-markdown python3-more-itertools python3-pygments python3-ttystatus python3-zipp Suggested packages: python3-xdg python-markdown-doc python-pygments-doc ttf-bitstream-vera The following NEW packages will be installed: cmdtest python3-cliapp python3-importlib-metadata python3-markdown python3-more-itertools python3-pygments python3-ttystatus python3-zipp 0 upgraded, 8 newly installed, 0 to remove and 1 not upgraded. Need to get 969 kB of archives. After this operation, 5201 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 python3-cliapp all 1.20180812.1-4 [44.5 kB] Get:2 http://archive.ubuntu.com/ubuntu jammy/main amd64 python3-more-itertools all 8.10.0-2 [47.9 kB] Get:3 http://archive.ubuntu.com/ubuntu jammy/main amd64 python3-zipp all 1.0.0-3 [5440 B] Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 python3-importlib-metadata all 4.6.4-1 [16.2 kB] Get:5 http://archive.ubuntu.com/ubuntu jammy/main amd64 python3-markdown all 3.3.6-1 [68.5 kB] Get:6 http://archive.ubuntu.com/ubuntu jammy/universe amd64 python3-ttystatus all 0.38-4 [14.7 kB] Get:7 http://archive.ubuntu.com/ubuntu jammy/universe amd64 cmdtest all 0.32.14.gcdfe14e-2 [21.9 kB] Get:8 http://archive.ubuntu.com/ubuntu jammy/main amd64 python3-pygments all 2.11.2+dfsg-2 [750 kB] Fetched 969 kB in 1s (911 kB/s) Selecting previously unselected package python3-cliapp. (Reading database ... 29455 files and directories currently installed.) Preparing to unpack .../0-python3-cliapp_1.20180812.1-4_all.deb ... Unpacking python3-cliapp (1.20180812.1-4) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../1-python3-more-itertools_8.10.0-2_all.deb ... Unpacking python3-more-itertools (8.10.0-2) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../2-python3-zipp_1.0.0-3_all.deb ... Unpacking python3-zipp (1.0.0-3) ... Selecting previously unselected package python3-importlib-metadata. Preparing to unpack .../3-python3-importlib-metadata_4.6.4-1_all.deb ... Unpacking python3-importlib-metadata (4.6.4-1) ... Selecting previously unselected package python3-markdown. Preparing to unpack .../4-python3-markdown_3.3.6-1_all.deb ... Unpacking python3-markdown (3.3.6-1) ... Selecting previously unselected package python3-ttystatus. Preparing to unpack .../5-python3-ttystatus_0.38-4_all.deb ... Unpacking python3-ttystatus (0.38-4) ... Selecting previously unselected package cmdtest. Preparing to unpack .../6-cmdtest_0.32.14.gcdfe14e-2_all.deb ... Unpacking cmdtest (0.32.14.gcdfe14e-2) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../7-python3-pygments_2.11.2+dfsg-2_all.deb ... Unpacking python3-pygments (2.11.2+dfsg-2) ... Setting up python3-ttystatus (0.38-4) ... Setting up python3-more-itertools (8.10.0-2) ... Setting up python3-zipp (1.0.0-3) ... Setting up python3-cliapp (1.20180812.1-4) ... Setting up python3-pygments (2.11.2+dfsg-2) ... Setting up python3-importlib-metadata (4.6.4-1) ... Setting up python3-markdown (3.3.6-1) ... Setting up cmdtest (0.32.14.gcdfe14e-2) ... Processing triggers for man-db (2.10.2-1) ... pi@MagicMirror-live:~$ sudo apt install -y nodejs Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: nodejs 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 28.5 MB of archives. After this operation, 52.4 MB of additional disk space will be used. Get:1 https://deb.nodesource.com/node_18.x jammy/main amd64 nodejs amd64 18.11.0-deb-1nodesource1 [28.5 MB] Fetched 28.5 MB in 1s (22.4 MB/s) (Reading database ... 29937 files and directories currently installed.) Preparing to unpack .../nodejs_18.11.0-deb-1nodesource1_amd64.deb ... Unpacking nodejs (18.11.0-deb-1nodesource1) over (16.17.1-deb-1nodesource1) ... Setting up nodejs (18.11.0-deb-1nodesource1) ... Processing triggers for man-db (2.10.2-1) ... pi@MagicMirror-live:~$ git clone https://github.com/MichMich/MagicMirror Cloning into 'MagicMirror'... remote: Enumerating objects: 23768, done. remote: Counting objects: 100% (1/1), done. remote: Total 23768 (delta 0), reused 1 (delta 0), pack-reused 23767 Receiving objects: 100% (23768/23768), 19.76 MiB | 12.35 MiB/s, done. Resolving deltas: 100% (14649/14649), done. pi@MagicMirror-live:~$ cd MagicMirror/ pi@MagicMirror-live:~/MagicMirror$ npm run install-mm > magicmirror@2.21.0 install-mm > npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev npm WARN config only Use `--omit=dev` to omit dev dependencies from the install. > magicmirror@2.21.0 postinstall > npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully! > " > magicmirror@2.21.0 install-vendor > echo "Installing vendor files ... > " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier Installing vendor files ... added 9 packages in 5s > magicmirror@2.21.0 install-fonts > echo "Installing fonts ... > " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier Installing fonts ... added 2 packages in 1s MagicMirror² installation finished successfully! > magicmirror@2.21.0 prepare > [ -f node_modules/.bin/husky ] && husky install || echo no husky installed. no husky installed. added 300 packages in 36s pi@MagicMirror-live:~/MagicMirror$ cp config/config.js.sample config/config.js pi@MagicMirror-live:~/MagicMirror$ npm run server > magicmirror@2.21.0 server > node ./serveronly [16.10.2022 13:16.02.218] [LOG] Starting MagicMirror: v2.21.0 [16.10.2022 13:16.02.225] [LOG] Loading config ... [16.10.2022 13:16.02.235] [LOG] Loading module helpers ... [16.10.2022 13:16.02.236] [LOG] No helper found for module: alert. [16.10.2022 13:16.02.252] [LOG] Initializing new module helper ... [16.10.2022 13:16.02.254] [LOG] Module helper loaded: updatenotification [16.10.2022 13:16.02.254] [LOG] No helper found for module: clock. [16.10.2022 13:16.02.513] [LOG] Initializing new module helper ... [16.10.2022 13:16.02.514] [LOG] Module helper loaded: calendar [16.10.2022 13:16.02.515] [LOG] No helper found for module: compliments. [16.10.2022 13:16.02.516] [LOG] No helper found for module: weather. [16.10.2022 13:16.02.536] [LOG] Initializing new module helper ... [16.10.2022 13:16.02.536] [LOG] Module helper loaded: newsfeed [16.10.2022 13:16.02.536] [LOG] All module helpers loaded. [16.10.2022 13:16.02.679] [LOG] Starting server on port 8080 ... [16.10.2022 13:16.02.695] [LOG] Server started ... [16.10.2022 13:16.02.696] [LOG] Connecting socket for: updatenotification [16.10.2022 13:16.02.696] [LOG] Starting module helper: updatenotification [16.10.2022 13:16.02.697] [LOG] Connecting socket for: calendar [16.10.2022 13:16.02.697] [LOG] Starting node helper for: calendar [16.10.2022 13:16.02.697] [LOG] Connecting socket for: newsfeed [16.10.2022 13:16.02.698] [LOG] Starting node helper for: newsfeed [16.10.2022 13:16.02.698] [LOG] Sockets connected & modules started ... [16.10.2022 13:16.02.698] [LOG] Ready to go! Please point your browser to: http://localhost:8080is this now right abd is the info “no helper module” O.K.?
best regards
P.S. when i put “http://localhost:8080” in the browser linie - it´s not going :-(
-
@kusselin remember, a container is a ‘system’
with its own IP address different than than the container hosting system (typically 172.xx.yy.zz)also, localhost means ONLY apps INSIDE this same ‘system’, can access… so that means a browser running IN the container… oops… not possible
SO, you have to change the MM config.js to allow apps OUTSIDE the container to access the MM app
and THEN on the container setup , map the container MM port to some host port … (so u can access from another pc, phone, tablet, outside the container hosting system )address:“0.0.0.0”.
ipWhitelist:[],you didn’t have to reinstall mm… one install runs three ways
full (ui on same ‘system’), npm start
server (ui on some OTHER system (have to change config) npm run server
client (just the UI part), npm run client -
@sdetweil what a fu…
now its running!!! Ohman!! yeahhhhhhh :-) thanks a lot…
o.k. i understand …in an lxc is not same as a pi with raspbia…because lxc is an container and has no graphic giu…then i have to start server (npm start server" right…
and i mut change the config as this here
address:“0.0.0.0”.
ipWhitelist:[], -
@kusselin yes, to help keep this organized for you
think of a container as a pi/nuc/laptop/extra machine with no display, running in text mode
and the only way to get to it is thru a proxy machine (your container host)and then some other machine, laptop, phone, tablet that wants to display info…
so other machine, phone, tablet connects to proxy, who forwards request to pi, and returns response back.
the proxy doesnt DO anything but transport the info . -
thanks sam…YOU ARE THE BEST :-)
-
one question: Where can i change the position from horizontal to vertical?
In what config can i change that?
-
@kusselin well that becomes much more troublesome…
the container doesn’t have display, so u can’t force it there
also, server mode doesn’t know orientation of display system .so this would typically be done on system w browser. full system in portrait or landscape.
I don’t know how you would do it just for one browser/tab…
-
ahh o.k. with installation on a pi there is the config.txt in boot an there you van change the display_rotate =1
O.K: in Container is difficult. Its ok. then thanks
-
@kusselin if u are running container on pi, AND displaying on pi, then it’s the same. if u are running container on windows, displaying on pi, it’s the same.
if displaying on windows, then have to turn windows portrait mode
-
@sdetweil said in MagicMirror install on proxmox LXC Container?:
if displaying on windows, then have to turn windows portrait mode
how is this going under win 10?
-
but there is a problem…when i started the server in the container with “npm run server” with putty… and i shut down the laptop the server is not reachable anymore :-(
means if I then eb on the ipad the 192.168.200.74:8080 enter the mirror is not accessible :-(
I have to enter again in putty then “npm run server” and then it is there…I shut down the laptop the server is no longer accessible :-(
What can be the reason for this now?
pi@MagicMirror-live:~/MagicMirror$ npm run server > magicmirror@2.21.0 server > node ./serveronly [16.10.2022 15:55.38.561] [LOG] Starting MagicMirror: v2.21.0 [16.10.2022 15:55.38.563] [LOG] Loading config ... [16.10.2022 15:55.38.566] [LOG] Loading module helpers ... [16.10.2022 15:55.38.567] [LOG] No helper found for module: alert. [16.10.2022 15:55.38.582] [LOG] Initializing new module helper ... [16.10.2022 15:55.38.582] [LOG] Module helper loaded: updatenotification [16.10.2022 15:55.38.583] [LOG] No helper found for module: clock. [16.10.2022 15:55.38.712] [LOG] Initializing new module helper ... [16.10.2022 15:55.38.712] [LOG] Module helper loaded: calendar [16.10.2022 15:55.38.713] [LOG] No helper found for module: compliments. [16.10.2022 15:55.38.713] [LOG] No helper found for module: MMM-OpenmapWeather. [16.10.2022 15:55.38.714] [LOG] No helper found for module: weather. [16.10.2022 15:55.38.722] [LOG] Initializing new module helper ... [16.10.2022 15:55.38.722] [LOG] Module helper loaded: newsfeed [16.10.2022 15:55.38.722] [LOG] No helper found for module: MMM-Traffic. [16.10.2022 15:55.38.723] [LOG] Initializing new module helper ... [16.10.2022 15:55.38.724] [LOG] Check MagicMirror² version for node helper 'MMM-Fuel' - Minimum version: 2.15.0 - Current version: 2.21.0 [16.10.2022 15:55.38.724] [LOG] Version is ok! [16.10.2022 15:55.38.724] [LOG] Module helper loaded: MMM-Fuel [16.10.2022 15:55.38.919] [LOG] Initializing new module helper ... [16.10.2022 15:55.38.921] [LOG] Module helper loaded: MMM-RNV [16.10.2022 15:55.39.141] [LOG] Initializing new module helper ... [16.10.2022 15:55.39.158] [LOG] Module helper loaded: MMM-PublicTransportHafas [16.10.2022 15:55.39.158] [LOG] Initializing new module helper ... [16.10.2022 15:55.39.158] [LOG] Module helper loaded: MMM-ioBroker [16.10.2022 15:55.39.209] [LOG] Initializing new module helper ... [16.10.2022 15:55.39.209] [LOG] Module helper loaded: MMM-COVID19-AMPEL [16.10.2022 15:55.39.211] [LOG] Initializing new module helper ... [16.10.2022 15:55.39.211] [LOG] Module helper loaded: MMM-SoccerLiveScore [16.10.2022 15:55.39.211] [LOG] No helper found for module: MMM-Snow. [16.10.2022 15:55.39.212] [LOG] No helper found for module: MMM-Carousel. [16.10.2022 15:55.39.212] [LOG] All module helpers loaded. [16.10.2022 15:55.39.277] [LOG] Starting server on port 8080 ... [16.10.2022 15:55.39.315] [WARN] You're using a full whitelist configuration to allow for all IPs [16.10.2022 15:55.39.321] [LOG] Server started ... [16.10.2022 15:55.39.332] [LOG] Connecting socket for: updatenotification [16.10.2022 15:55.39.332] [LOG] Starting module helper: updatenotification [16.10.2022 15:55.39.333] [LOG] Connecting socket for: calendar [16.10.2022 15:55.39.333] [LOG] Starting node helper for: calendar [16.10.2022 15:55.39.333] [LOG] Connecting socket for: newsfeed [16.10.2022 15:55.39.333] [LOG] Starting node helper for: newsfeed [16.10.2022 15:55.39.334] [LOG] Connecting socket for: MMM-Fuel [16.10.2022 15:55.39.334] [LOG] Starting module helper: MMM-Fuel [16.10.2022 15:55.39.334] [LOG] Connecting socket for: MMM-RNV [16.10.2022 15:55.39.449] [LOG] Connecting socket for: MMM-PublicTransportHafas [16.10.2022 15:55.39.450] [LOG] Connecting socket for: MMM-ioBroker [16.10.2022 15:55.39.451] [LOG] Connecting socket for: MMM-COVID19-AMPEL [16.10.2022 15:55.39.452] [LOG] Starting node helper for: MMM-COVID19-AMPEL [16.10.2022 15:55.39.452] [LOG] Connecting socket for: MMM-SoccerLiveScore [16.10.2022 15:55.39.453] [LOG] Starting node helper for: MMM-SoccerLiveScore [16.10.2022 15:55.39.453] [LOG] Sockets connected & modules started ... [16.10.2022 15:55.39.453] [LOG] Ready to go! Please point your browser to: http://0.0.0.0:8080and then this:
Ready to go! Please point your browser to: http://0.0.0.0:8080 ^C[16.10.2022 15:55.50.516] [LOG] [SIGINT] Received. Shutting down server... [16.10.2022 15:55.50.516] [LOG] Stopping module helper: updatenotification [16.10.2022 15:55.50.517] [LOG] Stopping module helper: calendar [16.10.2022 15:55.50.517] [LOG] Stopping module helper: newsfeed [16.10.2022 15:55.50.517] [LOG] Stopping module helper: MMM-Fuel [16.10.2022 15:55.50.517] [LOG] Stopping module helper: MMM-RNV [16.10.2022 15:55.50.517] [LOG] Stopping module helper: MMM-PublicTransportHafas [16.10.2022 15:55.50.517] [LOG] Stopping module helper: MMM-ioBroker [16.10.2022 15:55.50.518] [LOG] Stopping module helper: MMM-COVID19-AMPEL [16.10.2022 15:55.50.518] [LOG] Stopping node helper for: MMM-SoccerLiveScore -
Sam, can you help me? What stopped the Server when i closed the putty Software?
-
@kusselin
Hi,if your problem is only to keep the command running while/after you disconnected to the container you can use the “screen” command.
It you should be installed with Ubuntu already. If not you can install it withsudo apt update && sudo apt install -y screenYou then start a new screen with
screen -S NAMEwhile NAME is simply an alias and could be something like “mm”.
After this you can start the mirror with
npm run serverAnd you can leave the screen with the keyboard combination
CRTL+adThe screen then keeps running. If you want the resume to the screen you can use
screen -r NAME -
@kusselin when u disconnect a terminal session any app still running is terminated…
u can spinit off in the background with & at the end of the command
npm run server &
-
@sdetweil You are right in running apps with & in the background but if you disconnect the ssh session all background commands will be disconnected as well.
Either screen or a command like nohup needs to be used to keep the command running. -
@wishmaster270 never had one disconnected w &
-
@wishmaster270 said in MagicMirror install on proxmox LXC Container?:
@kusselin
Hi,if your problem is only to keep the command running while/after you disconnected to the container you can use the “screen” command.
It you should be installed with Ubuntu already. If not you can install it withsudo apt update && sudo apt install -y screenYou then start a new screen with
screen -S NAMEwhile NAME is simply an alias and could be something like “mm”.
After this you can start the mirror with
npm run serverAnd you can leave the screen with the keyboard combination
CRTL+adThe screen then keeps running. If you want the resume to the screen you can use
screen -r NAMEThanks, so it is going :-)
-
@kusselin and typically you would setup the container to run MM inside without user intervention… so none of those commands would be needed
-
@wishmaster270 said in MagicMirror install on proxmox LXC Container?:
npm run server
have today what changed at the mirror udn had to make reboot… now it no longer works :-(
After I executed the commands like :
screen -S MM (MM is the Name)
then
npm run server
and when i close the terminal the MMis stopping:-(
and the same when i going to cd /MagicMirror
and then i take this:
npm run server &
when i close the terminal MM is stopping…
what is my problem guys?
-
@sdetweil said in MagicMirror install on proxmox LXC Container?:
@kusselin and typically you would setup the container to run MM inside without user intervention… so none of those commands would be needed
Hi sam, unfortunately I have not yet understood why the server always stops when closing putty???
With the command npm run server I start the server… why does the container stop again?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login