official home-assistent app is not able to pull image

stillka

Explorer
Joined
Nov 15, 2014
Messages
55
Hello,

any idea whats wrong with the image? (Iam on latest TrueNAS-SCALE-22.12.0 and trying to install latest home-assistent app 2023.1.0_1.0.54)

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 14m default-scheduler Successfully assigned ix-home-assistant/home-assistant-6947797966-rj5jj to ix-truenas
Normal AddedInterface 14m multus Add eth0 [172.16.29.49/16] from ix-net
Normal Pulling 14m kubelet Pulling image "postgres:13.1"
Normal Pulled 13m kubelet Successfully pulled image "postgres:13.1" in 30.490562595s
Normal Created 13m kubelet Created container init-postgresdb
Normal Started 13m kubelet Started container init-postgresdb
Normal Pulled 13m (x2 over 13m) kubelet Container image "alpine:latest" already present on machine
Normal Created 13m (x2 over 13m) kubelet Created container init-configs
Normal Started 13m (x2 over 13m) kubelet Started container init-configs
Warning Failed 9m59s kubelet Failed to pull image "homeassistant/home-assistant:2023.1.0": rpc error: code = Unknown desc = context canceled
Warning Failed 7m34s (x2 over 11m) kubelet Failed to pull image "homeassistant/home-assistant:2023.1.0": rpc error: code = Unknown desc = context deadline exceeded
Warning Failed 7m34s (x3 over 11m) kubelet Error: ErrImagePull
Warning Failed 7m21s (x3 over 11m) kubelet Error: ImagePullBackOff
Normal BackOff 7m9s (x4 over 11m) kubelet Back-off pulling image "homeassistant/home-assistant:2023.1.0"

Thanks.
 

LarsR

Guru
Joined
Oct 23, 2020
Messages
719
i dont use home assisstant, but i just tried to install it and it downloaded and installed just fine for me.
 

stillka

Explorer
Joined
Nov 15, 2014
Messages
55
this workaround did the trick:

docker image pull homeassistant/home-assistant:2023.1.0
 

ye2enwbr

Cadet
Joined
Feb 21, 2023
Messages
1
It seems today's "Official" home-assistant is looking for a slightly different docker image. So I did the same work-around just now but with a different image version at the console:

sudo docker image pull homeassistant/home-assistant:2023.2.5

The "2023.2.5" part matches what I see in the available applications catalog under the home-assistant name.

The "layer" of the docker image with the hash of 55982f405be7 was about 318MB and that was the one I saw mentioned over and over in /var/log/k3s_daemon.log. But with that image pulled manually, home-assistant started without a hitch.

I recall a similar problem at my old company where some Kubernetes pods were not successfully deployed because we had too short of a timeout on the download for the needed Docker image. They just keep on trying and trying. In my case, I only get 30Mbps down, so that was probably a contributing factor. Would be a nice feature to be able to tweak that timeout in the app config if your having problems getting it to deploy.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
From the TrueCharts discord I learned that the timeout for pulling images was hardwired to 120 seconds. That's why manual pulling fixes deployment problems.
 
Top