1.30 update resets Homarr
Current docker compose:

Solution:Jump to solution
You did not follow the migration guide correctly:
https://homarr.dev/blog/2025/01/19/migration-guide-1.0
Hence, Docker did not persist your data and it was reset....
Migrate from 0.15.10+ to 1.0.0 | Homarr documentation
In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
14 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?
Solution
You did not follow the migration guide correctly:
https://homarr.dev/blog/2025/01/19/migration-guide-1.0
Hence, Docker did not persist your data and it was reset.
Migrate from 0.15.10+ to 1.0.0 | Homarr documentation
In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
Do you have a backup of the docker volume?
If not, your data is likely gone. This is not a Homarr issue but rather due to misconfiguration in the mounts / volumes and cannot be detected by Homarr. Make sure to properly follow the guides next time, we always announce breaking changes
Homarr 1.0 - complete rewrite of all systems | Homarr documentation
We proudly present to you - Homarr
1.0
.Nono, I was already using 1.29, I already migrated
I have a backup at least
Because everything just got deleted from the binded volumes
That's my point, migrating does work, but it will not persist your data if the container gets destroyed.
Here's what happened:
- You ran <1.0
- You migrated to 1.0 but did not update the mounts correctly
- You used Homarr normally
- You wanted to upgrade to 1.30 and Docker recreated the container.
That's... strange, I've been updating since 1.0
Please make sure that your compose is correct, before you restore your backup again: https://homarr.dev/docs/next/getting-started/installation/docker#installation
Docker | Homarr documentation
Docker is our recommended installation method for beginners and professionals.
Uh, so now it's appdata
Yes, correct.
See the breaking change list above ☝️ to see why 🙂
Welp, long live backups
Yes, absolutely. This is why backups are so important!
And sorry that you lost some data, sadly there isn't an easy way to alert the user for missing mounts. And Homarr can't know when it is storing data to a location that is not persisted.
Were you able to restore or do you still need time? Happy to assist you with the restore. And please make sure the mounts are correct now 🙂
No worry, I haven't lost anything, I do daily backups 😄
Can you let me know, when you were able to restore? I will mark this as resolved if you were able to.
Ye, resolve 🙂