Homarr•12mo ago

Failures building from source

I'm following the "Building from source" instructions here: https://homarr.dev/docs/introduction/installation After cloning and changing to the new directory, I run yarn install, after ~1 minute it exits with failures (way more than would be helpful to post here). Trying to install with npm install instead also fails with errors:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/i18next
npm ERR!   i18next@"^22.5.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@"^23.4.6" from [email protected]
npm ERR! node_modules/next-i18next
npm ERR!   next-i18next@"^14.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/<user>/.npm/_logs/2023-11-20T02_36_12_648Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/<user>/.npm/_logs/2023-11-20T02_36_12_648Z-debug-0.log

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/i18next
npm ERR!   i18next@"^22.5.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer i18next@"^23.4.6" from [email protected]
npm ERR! node_modules/next-i18next
npm ERR!   next-i18next@"^14.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/<user>/.npm/_logs/2023-11-20T02_36_12_648Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/<user>/.npm/_logs/2023-11-20T02_36_12_648Z-debug-0.log

I'm trying to build from source because docker-compose ends up in an infinite loop printing the following [sic]:

homarr    | ℹ Database is writeable
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Database is writeable
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Database is writeable

homarr    | ℹ Database is writeable
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Database is writeable
homarr    | ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
homarr    | ℹ Database is writeable

🚀 Installation | Homarr Docs

Homarr can be installed in many ways. For most users, Installation using Docker will be sufficient and the easiest.

14 Replies

ryab•12mo ago

FWIW --force and --legacy-peer-deps do not resolve the issue

explosive parrot•12mo ago

You can try deleting the database ./data/db.sqlite This will force it to reinitialise for your docker compose.

ryab•12mo ago

I've nuked the directory entirely a few times, just tried again deleting only data/db.sqlite specifically and I'm getting the same thing

explosive parrot•12mo ago

You can try replacing db.sqlite with a clean one here: https://discord.com/channels/972958686051962910/1172826100209025135/1173104601134805012

ryab•12mo ago

I think that I may have had a different issue entirely. While the instance writes that to the output indefinitely, when I navigate to <IP>:7575, I'm shown the page to add the data path, which says to refresh after adding it to the docker-compose.yml file (it was already there) and then click continue. I would stop the instance, make sure it was there, restart it, get back to that page and be told to do it again. I just continued past it and there seemingly isn't any issue

explosive parrot•12mo ago

do you mind showing me your docker-compose script? @ryab

ryab•12mo ago

It's literally just copied from the install instructions, though I did try messing around with it a bit before.

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.     #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/configs:/app/data/configs
      - ./homarr/icons:/app/public/icons
      - ./homarr/data:/data
    ports:
      - '7575:7575'

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.     #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/configs:/app/data/configs
      - ./homarr/icons:/app/public/icons
      - ./homarr/data:/data
    ports:
      - '7575:7575'

explosive parrot•12mo ago

Unfortunately this is beyond my expertise. They are usually on around 08h00 UTC

ryab•12mo ago

I'm fairly certain it's actually working now, just maybe with the quirk that I think those two lines about the database are being printed forever I have homarr up and just added radarr to it, so far so good. Still getting those lines printed, and I assume that if I hadn't created the admin account, it would still be prompting me to add that line to the docker-compose yaml and refresh

explosive parrot•12mo ago

Good to hear No rush, but could you do me a favour and restart the container at some time? If it was a one off, I'll call it gremlins; but if the repeating error returns I'll open an issue in github.

ryab•12mo ago

Nothing interesting in the logs after restarting

Starting homarr ... done
Attaching to homarr
homarr    | Exporting hostname...
homarr    | Migrating database...
homarr    | yarn run v1.22.19
homarr    | warning package.json: No license field
homarr    | warning ../package.json: No license field
homarr    | $ ts-node ./migrate.ts
homarr    | Done in 1.99s.
homarr    | Starting production server...
homarr    | Listening on port 7575 url: http://e877eb6a80f5:7575
homarr    |

Starting homarr ... done
Attaching to homarr
homarr    | Exporting hostname...
homarr    | Migrating database...
homarr    | yarn run v1.22.19
homarr    | warning package.json: No license field
homarr    | warning ../package.json: No license field
homarr    | $ ts-node ./migrate.ts
homarr    | Done in 1.99s.
homarr    | Starting production server...
homarr    | Listening on port 7575 url: http://e877eb6a80f5:7575
homarr    |

I did try multiple times and removed dirs etc before reaching out here. I couldn't tell you why it's working now 🤷‍♂️

explosive parrot•12mo ago

Gremlins it is!

ryab•12mo ago

I appreciate the help and the time either way

Manicraft1001•12mo ago

Hi, installing from source is not easy to do as you need specific requirements (node version, correct build tools, ...). It's normal to see the database message being logged many times - But does the application work at all when this message is being logged? Or why did you decide to switch to running from source?

Gaming

Programming

Failures building from source