MagicMirror install on proxmox LXC Container?

wishmaster270

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 with

sudo apt update && sudo apt install -y screen

You then start a new screen with

screen -S NAME

while NAME is simply an alias and could be something like “mm”.

After this you can start the mirror with

npm run server

And you can leave the screen with the keyboard combination

CRTL+ad

The screen then keeps running. If you want the resume to the screen you can use

screen -r NAME

sdetweil

@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 &

wishmaster270

@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.

sdetweil

@wishmaster270 never had one disconnected w &

kusselin

@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 with
sudo apt update && sudo apt install -y screen
You then start a new screen with
screen -S NAME
while NAME is simply an alias and could be something like “mm”.

After this you can start the mirror with
npm run server
And you can leave the screen with the keyboard combination
CRTL+ad
The screen then keeps running. If you want the resume to the screen you can use
screen -r NAME

Thanks, so it is going :-)

sdetweil

@kusselin and typically you would setup the container to run MM inside without user intervention… so none of those commands would be needed

kusselin

@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?

kusselin

@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?

sdetweil

@kusselin because that is the way it works. when the terminal window closes, any running app also is forced closed. it’s a security thing

during development I would not close the window. after you are happy, I would make the container auto start mm as part of it’s startup.
a containers design is to run ONE app.

I do not know how I do this w lxc containers
w docker, u add a property to the Dockerfile to tell what app to start

kusselin

@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 with
sudo apt update && sudo apt install -y screen
You then start a new screen with
screen -S NAME
while NAME is simply an alias and could be something like “mm”.

After this you can start the mirror with
npm run server
And you can leave the screen with the keyboard combination
CRTL+ad
The screen then keeps running. If you want the resume to the screen you can use
screen -r NAME

And what about this… yesterday i installed screen and i Type the Commander in putty and the Containers was already online…

Now, After an reboot Nottingham is Gong :-(