Home Assistant updates lose all settings (new install screen)

[PegFaceMan]

Describe the bug

Hi.
Seems after each Watchtower update of Home Assistant I lose everything and it's new install time.
I am using Docker and Portainer
No other containers have updated so far, so i'm worried the same will happen to those. I will need to disable Watchtower until I find a cause or setting to resolve.

Steps to reproduce

Watchtower update overnight

Expected behavior

Update not full re-install

Screenshots

No response

Environment

• Docker version 27.5.1 API 1.47 git commit 9f9e405
• Debian version 12 (Bookworm)
• Portainer version Community Edition 2.21.3

Your logs

INFO[41510] Found new homeassistant/home-assistant:latest image (543b62111c0c) 
INFO[41513] Stopping /HomeAssistsant (85d7ace09040) with SIGTERM 
INFO[41521] Creating /HomeAssistsant                     
INFO[41521] Removing image 7fa0101862f6                  
INFO[41536] Session done                                  Failed=0 Scanned=5 Updated=1 notify=no
INFO[84650] Session done                                  Failed=0 Scanned=5 Updated=0 notify=no
INFO[127851] Session done                                  Failed=0 Scanned=5 Updated=0 notify=no
INFO[171050] Session done                                  Failed=0 Scanned=5 Updated=0 notify=no
INFO[214294] Found new homeassistant/home-assistant:latest image (b278a9fefdec) 
INFO[214299] Stopping /HomeAssistsant (a5e30efc24e8) with SIGTERM 
INFO[214320] Creating /HomeAssistsant                     
INFO[214320] Removing image 543b62111c0c                  
INFO[214329] Session done                                  Failed=0 Scanned=5 Updated=1 notify=no

Additional context

No response

[github-actions]

Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏

[mervincm]

likely your home assistant is not using persistent storage. Your docker compose file or docker run command line needs to map persistent storage to the location that your image uses to store this configuration. If this is missing, it's not related to watchtower and you would see the problem occur regardless of how you pulled a newer image / deploy a new container.

[PegFaceMan]

Thank you for your response. This makes sense and gives me a great starting point to investigate further.
I'll go back to Portainer and/or Home Assistant as my issue lies in that direction and my configuration when i set it up.
Thanks again