You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not use the docker image because I use LXC containers on proxmox. I have successfully installed it but thee are some caveats:
On the documentation for the non dockerized installation it is a prerequisite to install (obviously) npm. npm is not installed within node on some distributions. For Debian 12 bookworm you have to install node AND npm.
When you create the LXC container assign at least 4GB of RAM. The npm build process will fail if because of lack of resources (HEAP memory). Also as a precaution assign more RAM to node with the following env variable:
export NODE_OPTIONS=--max-old-space-size=4096
Once flame is compiled and running yo can reduce the amount of RAM to 512MB and will run without issues.
You can create a systemd service to run the application,if not, you have to manually run it each time the machine is rebooted:
a. Create system service on /lib/systemd/system/flame.service
b. Add the following content (adapt the flame project folder location, user and password to your liking):
Hi team!
Just informative.
I do not use the docker image because I use LXC containers on proxmox. I have successfully installed it but thee are some caveats:
On the documentation for the non dockerized installation it is a prerequisite to install (obviously) npm. npm is not installed within node on some distributions. For Debian 12 bookworm you have to install node AND npm.
When you create the LXC container assign at least 4GB of RAM. The npm build process will fail if because of lack of resources (HEAP memory). Also as a precaution assign more RAM to node with the following env variable:
export NODE_OPTIONS=--max-old-space-size=4096
Once flame is compiled and running yo can reduce the amount of RAM to 512MB and will run without issues.
a. Create system service on /lib/systemd/system/flame.service
b. Add the following content (adapt the flame project folder location, user and password to your liking):
systemctl daemon-reload.
systemctl enable flame.service
systemctl start flame.service
You are good to go. You can now power off the LXC container and assign 512MB or even less of RAM and flame will work.
I have it running on a LXC container with 512MB or RAM, 6GB of hardisk and two cores and it is essentially not consuming resources:
The text was updated successfully, but these errors were encountered: