7 ms·

I have it in docker a d use supervised mode (which seems discouraged, but I want my machine for other uses also). The one thing I struggle with is updating, I'm

I have it in docker a d use supervised mode (which seems discouraged, but I want my machine for other uses also). The one thing I struggle with is updating, I'm concerned if I update it'll break. Is there a way to fully snapshot a container state and it's disk state, so I can 100% restore to it if something goes wrong ? I'm still running HA from 2020 because of this. The other think I'm not a huge fan of is it's template language, it's clunky to say the least, but overall it's a great amd flexible system

apexalpha 1y ago
I just backup the folder (volume) and that’s it. If I should ever need to rollback I can change the Docker image tag from ‘latest’ to a specific one I guess. I’ve never had to do it but I do know people sometimes complain about updates breaking things.
baq 1y ago
I’m running it with docker compose for the same reason and it never failed an update, but there was an occasional config tweak required. For the most part it’s compose pull, compose up, check back in a couple weeks for the point release. Updating from that far is probably risky but you don’t need to backup everything, just the config directory. Automated backups to Google drive are worth the upgrade alone.
acidburnNSA 1y ago
In the last few releases they've polished the built in backup and restore features, which are available in the setting menu now. https://www.home-assistant.io/integrations/backup/ https://www.home-assistant.io/integrations/backup/
ImPostingOnHN 1y ago
> Is there a way to fully snapshot a container state and it's disk state `docker commit` should help you there, in making a copy of the container
mmmpetrichor 1y ago
All the persistent storage is in the host directory path you map into the container. Just backup the directory you're mapping into the container. Don't try to save the container state.
Calwestjobs 1y ago
some filesystems support snapshots for directories. your software does not have to have "compatibility" for it, it just works. with BTRFS you can even mount/work with multiple snapshots of same directory at once. it is great for debugging. deduplication will save you space.
Hikikomori 1y ago
Could run it in a VM instead.

apexalpha 1y ago

I just backup the folder (volume) and that’s it. If I should ever need to rollback I can change the Docker image tag from ‘latest’ to a specific one I guess. I’ve never had to do it but I do know people sometimes complain about updates breaking things.

baq 1y ago

I’m running it with docker compose for the same reason and it never failed an update, but there was an occasional config tweak required. For the most part it’s compose pull, compose up, check back in a couple weeks for the point release. Updating from that far is probably risky but you don’t need to backup everything, just the config directory. Automated backups to Google drive are worth the upgrade alone.

acidburnNSA 1y ago

In the last few releases they've polished the built in backup and restore features, which are available in the setting menu now. https://www.home-assistant.io/integrations/backup/ https://www.home-assistant.io/integrations/backup/

ImPostingOnHN 1y ago

> Is there a way to fully snapshot a container state and it's disk state `docker commit` should help you there, in making a copy of the container

mmmpetrichor 1y ago

All the persistent storage is in the host directory path you map into the container. Just backup the directory you're mapping into the container. Don't try to save the container state.

Calwestjobs 1y ago

some filesystems support snapshots for directories. your software does not have to have "compatibility" for it, it just works. with BTRFS you can even mount/work with multiple snapshots of same directory at once. it is great for debugging. deduplication will save you space.

Hikikomori 1y ago

Could run it in a VM instead.