Hi,
The release notes of Home Assistant OS 17 mention that you could migrate to a new storage driver to take advantage of improved performance.
In the HA CLI, you should run “ha docker migrate-storage-driver” and then reboot HAOS.
But how do I know this migration is done successfully (or not)? I can’t find it in the logs.
I’ve performed this update on my test system, and watched carefully during the reboot as I expected to see some kind of information being displayed. Other than the fact that docker took longer to start, nothing was visible. So, I too wonder how we can check this went through ok, other than the fact it all started successfully afterwards.
Looking in the host and supervisor logs I think I can see the migration, but there are some scary errors errors associated with docker scripts so I do hope everything worked ok!
I ran this command (via advanced terminal addon), it took about 10 minutes for my HA to come back up, but no apparent errors or notification of completion that I saw.
I saw this screen too. Waited about 10 minutes and HA got up by itself without any errors.
Maybe someone who did not execute the command yet can post what HA tells here. This is my output after executing.
➜ ~ ha docker info
enable_ipv6: null
logging: journald
mtu: null
registries: {}
storage: overlayfs
version: 29.1.3
have not done the migration yet
➜ ~ ha docker info
enable_ipv6: null
logging: journald
mtu: null
registries: {}
storage: overlay2
version: 29.1.3
I have the same thing (after executing the command). So I guess this is the way to verify. Thanks!
this leaves the question why isn’t this automated
Hi everyone,
I guess I have to apply the 17.0 update before docker migration?
Cause it is dangerous.
My system seems to be completely broken now.
cant start hassio_supervisor here anymore
I think it did the migration but somehow no dockers are there anymore…
oh well thank god I took a backup like recommended…
I assumed that is why they emphasized to have a full backup before doing it.
I just did the update and the migration. It all went fine, but the migration did take a bit over 10 heart racing minutes on my HA Yellow. There is nothing I like less than an upgrade where there is no way to tell what’s going on.
not even 5 minutes and everything is up and running again
HA Yellow with CM5.
I can imagine the part where all the add-ons are reloaded is frustrating because that means the SSH option gets broken
RPI 5. Worked fine. Was a bit tense waiting. No idea what the improvement is.
I’ve been sitting on this as well for 30ish minutes so far, running in a HyperV VM. A bit too nervous to give it a reboot just yet.
30 minutes at that spot I don’t think is normal, but I’m by no means an expert. Mine finally completed about 5 minutes after I posted.
