Open bigjimmy546 opened 10 months ago
I have the same issue, also hosted on Synology.
Do you know where the synology config is ? I’m not familiar with it. What was your installation process like ?
I've actually just redeployed the container and it completed the upgrade process correctly. I did mine using docker run from the Synology CLI via SSH. I have Portainer running, so I get the logs from that.
My run command was like this;
docker run \ --name homarr \ --restart unless-stopped \ -p 7575:7575 \ -v /volume3/docker/homarr/configs:/app/data/configs \ -v /volume3/docker/homarr/data:/data \ -v /volume3/docker/homarr/icons:/app/public/icons \ -v /var/run/docker.sock:/var/run/docker.sock \ --label=com.centurylinklabs.watchtower.monitor-only=true \ ghcr.io/ajnart/homarr:latest
Unless you are running Watchtower you won't need the label, the paths will need to be updated to suit you deployment. Hopefully that works for you.
I've actually just redeployed the container and it completed the upgrade process correctly. I did mine using docker run from the Synology CLI via SSH. I have Portainer running, so I get the logs from that.
My run command was like this;
docker run --name homarr --restart unless-stopped -p 7575:7575 -v /volume3/docker/homarr/configs:/app/data/configs -v /volume3/docker/homarr/data:/data -v /volume3/docker/homarr/icons:/app/public/icons -v /var/run/docker.sock:/var/run/docker.sock --label=com.centurylinklabs.watchtower.monitor-only=true ghcr.io/ajnart/homarr:latest
Unless you are running Watchtower you won't need the label, the paths will need to be updated to suit you deployment. Hopefully that works for you.
You mention the synology cli, so there is no way to install homarr simply with a GUI right ? If yes then they might have an outdated “template” to correctly set the app up. if you’re using docker manually and encountering issue with file permissions we recommend trying to use homarr without mounting a database
The only way I know to do it via the GUI would be using a task, the way Marius hosting describes it. Only really saves connecting to the CLI directly, which personally I find easier.
I think in my case something went wrong with the upgrade when I previously tried it, removing the container and starting again sorted it out and now it is running fine.
I also installed in ubuntu using docker compose, my config are as follow
GNU nano 6.2 docker-compose.yml
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:
- ./homarr/configs:/app/data/configs
- ./homarr/data:/data
- ./homarr/icons:/app/public/icons ports:
- '7575:7575'
the issue occurred even before I upgrade to v0.14.1, that's why I upgraded.
Added ./homarr/data:/data
both version has this issue (forgot what version I had before)
I also installed in ubuntu using docker compose, my config are as follow
GNU nano 6.2 docker-compose.yml 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:
- ./homarr/configs:/app/data/configs
- ./homarr/data:/data
- ./homarr/icons:/app/public/icons ports:
- '7575:7575'
the issue occurred even before I upgrade to v0.14.1, that's why I upgraded. Added
./homarr/data:/data
both version has this issue (forgot what version I had before)
We fixed it in v14.1, try to delete ./homarr/data
We fixed it in v14.1, try to delete ./homarr/data
I'm was using 14.1 and the issue persist, did another brand new install in Ubuntu, same issue. Thanks
Hello 👋, this issue has been open for 60 without activity. Please close this issue if it's no longer relevant or has been resolved. Still relevant? Simply reply and I'll mark it as active.
Is this still an issue?
Environment
Docker
Version
v0.14.1
Describe the problem
Installed via Synology container Manager, after the onboard process, site show error going to the board. tried again in Ubuntu, using docker compose, same error occurs.
attached is the error from Synology container manager.
Logs
No response
Context
Please tick the boxes