Upgrading a docker image

Installation
1

Hi I was hoping the upgrade option in lovelace would work, , but looks like not implmentsed in the June 26 edition
so From Docker CLI and upgrade.

# finally, start a new one
docker run -d \
  --name homeassistant \
  --restart=unless-stopped \
  --privileged \
  -e TZ=MY_TIME_ZONE \
  -v /PATH_TO_YOUR_CONFIG:/config \
  -v /run/dbus:/run/dbus:ro \
  --network=host \
  ghcr.io/home-assistant/home-assistant:stable

Question : if left exactly as above, do I enter TZ, or will it pick up that its UTC, and likewise the path to config , everything homeassistant is in /srv/homeassistant , has that to be entered , or as default used.

Sorry about the daft questions
TIA

2

Hard to understand what you were asking but I hope I answer them…

1.if it specified with -e TZ=MY_TIME_ZONE it will not go to utc automatically because that variable is literally defined.
If you leave it to -e TZ=MY_TIME_ZONE i think it will (maybe?) fail because that timezone does not exist, so just assign your timezone. In my case it would be

-e TZ=Europe/Berlin

/PATH_TO_YOUR_CONFIG refers to a path where several files like the configuration.yaml will be saved on your server. So if you have /srv/homeassistant make it:

-v /srv/homeassistant/:/config \
3

Thanks that answers the questions,
my configuration.yaml file ia in /home/odroid.homeassistant
so
-v /home/odroid.homeassistant/ : /config
and -e TZ=Europe/London

Hope I have understood that correctly thanks

4

Up and running on latest version, thanks for the help

5

I’d recommend you switch to docker compose. Also there’s a update instruction here for docker run.

6

I did consider that , and loaded docker compose, but if I try to run a command I get an error message that there is no config file.

7

You need to create a compose.yaml with the content as shown in the link. You can use nano compose.yaml to create it. If you share exactly what yo usee I might be able to tell you more. Compose makes it easier to upgrade later. There’s a converter here too but I only recommend this if you are somewhat familiar with docker already to be able to validate its output.