All make sense. Problem is that the official install docs don’t seem to cover this, thus when you follow their updates steps you could lose data or at least not have your data loaded into the updated container.
For example this is the install doc command.
docker run -d --name="home-assistant" -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/raspberrypi3-homeassistant
This downloads an image with no tags (docker images shows TAG=
The update command listed is
sudo docker pull homeassistant/home-assistant:latest which downloads an image with tag
… and that’s it. No further instructions for update aside from “restart” which doesn’t update the container. When I fire up another container using the original install command but specify the
latest image it does not pull from my configs in /PATH_TO_YOUR_CONFIG (which of course I updated with my actual path). I also switch the image to
homeassistant/raspberrypi2-homeassistant to match my pi. I need to go back to see if I made a mistake when updating the /PATH_TO_YOUR_CONFIG when running the latest image. Hoping that’s all it is.