Homarr v1 released

[CrazyWolf13]

Hi
Homarr v1 has just been released, can't wait to see the script updated to v1.

https://homarr.dev/docs/getting-started/
https://github.com/homarr-labs/homarr

Note a manual import/export is necessary, so maybe it would be better to either replace or make a new lxc script under a different name.

[MickLesk]

@michelroegl-brunner can you check it?

[michelroegl-brunner]

Sure can.

[hbast]

any news on this?

As far as I know there is no automatic migration mechanism from “pre v1” to v1. Exporting the current config and re-importing after update is the process.

See official migration guide https://homarr.dev/docs/getting-started/after-the-installation/#importing-a-zip-from-version-before-100
See also #887

[Shotafry]

will u create a new Script? in theory i have all the requisites and backups of my boards ready to install in the new Homarr LXC.

[knario]

Hi, without wanting to trash this request for the new homarr v1, I would hold out for a while with the version we have in the community.
There are lots and lots of requests for scripts and that takes a lot of time and effort from people in the know.
To try things out and learn something along the way, I have been using ChatGpt for several days to try to adapt some services to proxmox lxc and so far I have managed to install some services.

• Castopod.
• FreshRss
• Xfce desktop and another plasma one to connect to guacamole.
• local-content
• DoneTick

It's a bit of trial and error and a lot of frustration because the AI fails, but it's worth it to see that we can get something for ourselves.

[CrazyWolf13]

@knario While that is true I see absolutely 0 reason to hold this back.

That's nice that you were able to adapt these services to Proxmox, but I'm not sure why this is related here?
Also why don't you share what you achieved by creating Pull Requests, so everyone could benefit? :)

[knario]

Hi, I wish I knew how to create a Pull Requests so that all members of the community could benefit.
What I could do is to share the commands that chatGpt gave me to create the services, although I tell you that it failed a lot and it is not something that comes out the first time. But I can share it :-)

[MickLesk]

https://github.com/community-scripts/ProxmoxVE/tree/main/.github/CONTRIBUTOR_GUIDE
https://github.com/community-scripts/ProxmoxVE/blob/main/.github/CONTRIBUTING.md

[MickLesk]

#1825

PR is available, please install an new LXC and Test.

[Narkowii]

I try on a new install :

⚙️ Using Default Settings on node proxmox
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 130
🚀 Creating a Homarr LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Container 130 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.167
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.121.3
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up Node.js Repository
✔️ Installed Node.js/pnpm
⠧ Installing Homarr (Patience)
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1

[ocr99]

Same error here :(

[MickLesk]

Im not. Run in verbose?

[ocr99]

Running in verbose:

@homarr/nextjs:build: <--- Last few GCs --->
@homarr/nextjs:build: 
@homarr/nextjs:build: [7946:0x350c9000]    68955 ms: Mark-Compact 984.4 (1044.1) -> 974.7 (1047.0) MB, pooled: 0 MB, 693.24 / 0.00 ms  (average mu = 0.201, current mu = 0.104) allocation failure; GC in old space requested
@homarr/nextjs:build: [7946:0x350c9000]    69679 ms: Mark-Compact 974.7 (1047.0) -> 974.7 (1047.0) MB, pooled: 0 MB, 723.80 / 0.00 ms  (average mu = 0.107, current mu = 0.000) allocation failure; GC in old space requested
@homarr/nextjs:build: 
@homarr/nextjs:build: 
@homarr/nextjs:build: <--- JS stacktrace --->
@homarr/nextjs:build: 
@homarr/nextjs:build: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
@homarr/nextjs:build: ----- Native stack trace -----
@homarr/nextjs:build: 
@homarr/nextjs:build:  1: 0xe3811e node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
@homarr/nextjs:build:  2: 0x125fb70 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
@homarr/nextjs:build:  3: 0x125fe47 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
@homarr/nextjs:build:  4: 0x148d885  [node]
@homarr/nextjs:build:  5: 0x148d8b3  [node]
@homarr/nextjs:build:  6: 0x14a696a  [node]
@homarr/nextjs:build:  7: 0x14a9b38  [node]
@homarr/nextjs:build:  8: 0x1ce63d1  [node]
 ⠧@homarr/nextjs:build: Aborted
@homarr/nextjs:build:  ELIFECYCLE  Command failed with exit code 134.
 ⠇@homarr/nextjs:build:  ELIFECYCLE  Command failed with exit code 134.
@homarr/nextjs:build: ERROR: command finished with error: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (134)
@homarr/nextjs#build: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (134)

 Tasks:    4 successful, 5 total
Cached:    0 cached, 5 total
  Time:    1m14.377s 
Failed:    @homarr/nextjs#build

>   ...Finishing writing to cache...                                                                                                 WARNING  no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json`
 WARNING  no output files found for task @homarr/db#build. Please check your `outputs` key in `turbo.json`
 WARNING  no output files found for task @homarr/tasks#build. Please check your `outputs` key in `turbo.json`
 WARNING  no output files found for task @homarr/websocket#build. Please check your `outputs` key in `turbo.json`
 ERROR  run failed: command  exited (134)
 ⠏ ELIFECYCLE  Command failed with exit code 134.

[ERROR] in line 63: exit code 0: while executing command $STD pnpm build

[MickLesk]

Done

[krazos]

It appears to be running out of memory during the build. I was getting the same error, but was able to get it to install by bumping the RAM allocation to 4GB.

[ocr99]

Can confirm it works!

[MickLesk]

Done

[DAmadeusM]

How to update homarr to new release? do I need to build new lxc?

[MickLesk]

Yep

[DAmadeusM]

How to backup apps integrations and dashboards?

[MickLesk]

@CrazyWolf13

[CrazyWolf13]

Hi
@DAmadeusM
Here is the guide from homarr: https://homarr.dev/docs/getting-started/after-the-installation#importing-a-zip-from-version-before-100

If you don't have the option to export the zip files, it may get a bit complicated, we need to manually update homarr.
This goes with the following commands:

RELEASE=$(curl -s https://api.github.com/repos/ajnart/homarr/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')
systemctl stop homarr
mkdir -p /opt/homarr-data-backup
cp /opt/homarr/.env /opt/homarr-data-backup/.env
cp /opt/homarr/database/db.sqlite /opt/homarr-data-backup/db.sqlite
cp -r /opt/homarr/data/configs /opt/homarr-data-backup/configs
wget -q "https://github.com/ajnart/homarr/archive/refs/tags/v${RELEASE}.zip"
unzip -q v${RELEASE}.zip
rm -rf v${RELEASE}.zip
rm -rf /opt/homarr
mv homarr-${RELEASE} /opt/homarr
mv /opt/homarr-data-backup/.env /opt/homarr/.env
cd /opt/homarr
yarn install &>/dev/null
yarn build &>/dev/null
rm -rf /opt/homarr/data/configs
mv /opt/homarr-data-backup/configs /opt/homarr/data/configs
mv /opt/homarr-data-backup/db.sqlite /opt/homarr/database/db.sqlite
yarn db:migrate &>/dev/null
rm -rf /opt/homarr-data-backup
systemctl start homarr

This is pulled from the old update script:
https://github.com/community-scripts/ProxmoxVE/blob/15f04d525d2d3e4c4c53f3848abe0bb40014f831/ct/homarr.sh

After this the export should be available, you can export your data and create a new LXC, which will then install homarr v1, where you can import that zip again.

[razulian]

In other words: the migration functionality for old Homarr was added in v0.15.10, which was the last version of the old repo. If you are on an older version like me (e.g. v0.15.7), you'll first need to install the update from the old Homarr-repo before following the migration instructions.
The Proxmox community script for installing Homarr was updated and doesn't point to the old repo anymore. The following line can be run instead of update and will get you to v0.15.10. It points to an archived version of the community script from 1 january 2025 instead of the latest one.
bash -c "$(wget -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/15f04d525d2d3e4c4c53f3848abe0bb40014f831/ct/homarr.sh)"

Then follow the migration guide to Homarr V1: https://homarr.dev/blog/2025/01/19/migration-guide-1.0