New container showing default board, not my created ones.
Kinda at my wits end. I tried typing the long version with as much detail as possible but ran out of characters. TLDR User is dumb and would appreciate help. If this support is outside the scope of this discord, no worries and thank you for working on this project and sharing it with me. I feel like I'm missing something quite simple though.
I'm on Synology and have a working container with 0.15.10 but I'm having trouble duplicating it and running via docker compose. I tried migrating to latest successfully with docker compose and was having some issues with the book marks and generally found it not preferable to 0.15.10. My plan was to migrate the original container to also use docker compose but keep it on 0.15.10. then I would run them side by side and migrate again when ready.
I now have three folders and containers. :
1. /docker/homarr (Working original folder set up by backwards old synology method I found somewhere. Not enough characters to elaborate but maybe not even relevant)
2. /docker/homarr_latest (Working 1.4 with migrated dashboards set up with docker compose)
3. /docker/homarr-0.15.10 (This folder is an exact copy of the original /homarr with the exact same default.json and links.json boards with all my customizations in them.)
My docker compose for 3 is below. It is very similar to what is being used for 1 but I don't get my boards, it just shows default.
services:
homarr:
container_name: homarr_0.15.10
image: ghcr.io/ajnart/homarr:0.15.10
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- /volume1/docker/homarr-0.15.10:/appdata
- /volume1/docker/homarr-0.15.10/icons:/app/public/icons
- /volume1/docker/homarr-0.15.10/data:/data
ports:
- '4755:7575'Solution:Jump to solution
Bolded volume was wrong. I guess I copied my YAML for 1.4 and the location in the container changed between versions. Hours lost because I don't know what I'm doing. Oh well. Thanks for all the hard work. Looking forward to giving version 1 a try again soon when I have some time to clean it up.
services: homarr: container_name: homarr_0.15.10...
3 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Wait I just figured it out.
Solution
Bolded volume was wrong. I guess I copied my YAML for 1.4 and the location in the container changed between versions. Hours lost because I don't know what I'm doing. Oh well. Thanks for all the hard work. Looking forward to giving version 1 a try again soon when I have some time to clean it up.
services: homarr: container_name: homarr_0.15.10 image: ghcr.io/ajnart/homarr:0.15.10 restart: unless-stopped volumes: - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration - /volume1/docker/homarr-0.15.10:/app/data/configs - /volume1/docker/homarr-0.15.10/icons:/app/public/icons - /volume1/docker/homarr-0.15.10/data:/data ports: - '4755:7575'