MH4K
(Martin)
March 30, 2023, 8:36pm
1
Hi,
I updated my Home Assistant and afterwards it wants me to create a new user. So I guess it didn`t find my config!?
I did the following:
“ls -l” and found folder “homeassistant” assuming it contains my config.
docker pull ghcr.io/home-assistant/home-assistant:stable
docker stop homeassistant
docker rm homeassistant
docker run -d \
--name homeassistant \
--privileged \
--restart=unless-stopped \
-e TZ=Europe/Berlin \
-v /homeassistant:/config \
--network=host \
ghcr.io/home-assistant/home-assistant:stable
Did I do anything wrong in this case?
Regards
Martin
Tinkerer
(aka DubhAd on GitHub)
March 30, 2023, 8:40pm
2
That looks fine - can it write to /homeassistant
?
Also, if you use compose files you can just do:
docker compose pull homeassistant
docker compose up -d homeassistant
MH4K
(Martin)
March 30, 2023, 8:43pm
3
Thanks for the feedback. How do I find out if it can write to /homeassistant?
I`ll try docker compose next time as it looks more easy and safe to use
Tinkerer
(aka DubhAd on GitHub)
March 30, 2023, 8:51pm
4
When you ran the command originally it’ll have created files in /homeassistant
- are there any there older than when you started HA this time?
Unless of course you had a different path there originally…
MH4K
(Martin)
March 30, 2023, 8:57pm
5
I dont know. Well, I
ll just configure it a second time and be a bit more cautious next time…
I just tried this:
And even if I just created an account etc. there doesn`t seem to be a config-file?
remlei
(Remlei)
March 30, 2023, 11:36pm
6
updating containers is usually a 1 click job with portainer.
try looking at you /homeassistant directory if the files are still there, if its there, try giving it a 777 permission on that directory and respin th container.