Home-Assistant - Docker - How to make truly persistent

HA takes a lot of setup and tweaking so data persistence is a must. I recently re-created my docker container and moved the config directory using mv * conf/ but started it up to find many things needed re-setup such as my integrated devices and custom lovelace UI.

What other volumes besides “/config” do I need to map to make this 100% persistent?

That should be it actually.

I copied my “conf” directory, so all my .yaml was loaded, but it seems that when you “take control” of lovelace, that is stored elsewhere. For sure my “config” directory is being correctly mapped, as it did pickup my customizations such as 3rd party integrations I manually downloaded (I don’t use supervisd). Also, the devices that I setup via “integrations” like my Roku TV, Epson Printer and Apple Homekit accessories are all showing as needing to be setup again.

@Tediore perhaps I should be filing a bug report? Would that be on github?

Looks like you might have missed the hidden .storage directory in /config where many things are stored.

1 Like

Actually, you don‘t copy the configuration directory, you just „mount“ it as a volume to the container. This way data is stored outside the container and persistent.

@Tediore You sir, just saved me a few hours. Thank you! I hate how “mv * conf/” doesn’t catch those hidden files/dirs/ There was actually a bunch of folders left in the old location which I thankfully didn’t wipe, but I did move everything up into it’s own directory and missed that stuff.

Thanks again!