Seems you are using the image provide by synology registry, I am not sure how / where this ‘latest’ is mapped to but try to download 2023.11.2 (it is visible in the registry list)…and recreate your container afterwards
I am not sure what to say now, I expected you to know a bit how containers work so am hesitant to provide high level things that may destroy your HA.
Your container should have a volume on one of your drives mapped to ‘config’
by recreating the container you still map to that volume.
Let’s do one step back…after you downloaded ‘latest’ what did you do next?
Container Manager shows under Image whether an update of a container is available, and you can use it to perform the refresh also. I am very satisfied with this new functionality in Container Manager, works flawless for all my containers including HA.
docker pull homeassistant/home-assistant:latest
latest: Pulling from homeassistant/home-assistant
Digest: sha256:400f20c77f52ac31334c1e73a2f19b2d6e5820757d1d476f01960b1efed31949
Status: Image is up to date for homeassistant/home-assistant:latest
docker.io/homeassistant/home-assistant:latest
The way you setup your container, it’s explicitly using the 2023.02.0 image. No matter how many other images you download, your container will always use that one. Someone else suggested, and I concur, that you need to get some understanding about how containers work. You either need to update the docker compose file or the docker run command to use the new image OR you need to change so that the docker setup is looking at the LATEST tag, which makes updating easier.
I have no clue what you did but normally you’d have a volume defined that refers to /config…that (persistent) volume would contain the settings. When you refesh the container, the new one still needs to point to that volume and picks up where the previous one left off.
So: did you set up a volume and is this (again) connected to the new container?