Update HA on Synology Docker

Hi,

Not sure if this is the correct category, so please let me know if i need to move this elsewhere.

I’m trying to update HA 2023.2.5 to the latest version on my Synology DS218+ with Docker.

The system download the latest version but on HA i can’t see the update, still appear the 2023.2.5.

How can i solved it ?

Thanks

Did you re-create the container and/or is the container pointing to this image?

I’ve only one image.

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’ve download the latest from registry but nothing happend.

if i download the 2023.11.2 create a new image, so if i create a new container i lost the settings of HA ?

Thanks

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?

Forget about my image container name and version below…this is what I have ( I have 4 different installs for playground/dev reasons)

And maybe check this for guidance…
How to Install Home Assistant on Your Synology NAS – Marius Hosting

EDIT : or what guide/doc/process did you follow for your current install?

After download ‘latest’ i’ve restarted the container.

Yes i followed that guide.


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.

Yes i know, i’ve update with that functionality. But i don’t know why don’t update the system on HA.

You update to home.assistant:2023.2.0 every time. You should go for home.assistant:latest to obtain the latest version

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

now i’ve two images

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.

As per the web…this is how you update the container and repeating…do read a bit more :slight_smile:

  1. Go to Registry and download new image (mostly the “latest” version)

this you did

  1. Go to Container, select the container you need to update and stop it
  2. From Actions menu select “Clear” or under DSM7 this command has been renamed “Reset”.*
  3. Start the container again
1 Like

my fault… I was looking for clean and couldn’t find the entry, it was the only step I was missing, now I see the latest updated version.
Thank you :slight_smile:

I missed the last step, resetting the container…

I did this and all my settings are gone.
Can i roll back anyhow?

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?

How to Install Home Assistant on Your Synology NAS – Marius Hosting
This gut likes to work with a script but that is not really needed in essence…a choice

Thanks for the fast reply!
I did not touch anything volume related.
Just executed steps 1-4 from post #15 which was marked as solution.