I’m trying to install HassOS in VMware Fusion but keep getting the following error. This is strange because it also says I have 28 gb of free space. I tried logging into the cli and and can ping google OK.
Any ideas?
Updating image homeassistant/qemux86-64-homeassistant:landingpage to homeassistant/qemux86-64-homeassistant:0.118.4
Downloading docker image homeassistant/qemux86-64-homeassistant with tag 0.118.4.
Updating service information
Updating local network information
Can’t install homeassistant/qemux86-64-homeassistant:0.118.4 → 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.118.4: No such image: homeassistant/qemux86-64-homeassistant:0.118.4”).
This error is often caused by not having enough disk space available. Available space in /data is: 28.6 GiB
Error on Home Assistant installation. Retry in 30sec
Updating image homeassistant/qemux86-64-homeassistant:landingpage to homeassistant/qemux86-64-homeassistant:0.118.4
Downloading docker image homeassistant/qemux86-64-homeassistant with tag 0.118.4.
Can’t install homeassistant/qemux86-64-homeassistant:0.118.4 → 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.118.4: No such image: homeassistant/qemux86-64-homeassistant:0.118.4”).
This error is often caused by not having enough disk space available. Available space in /data is: 28.6 GiB
Error on Home Assistant installation. Retry in 30sec
Am having similar issues here. Two types of errors I am getting are:
20-11-29 07:29:57 INFO (MainThread) [supervisor.api.security] /core/update access from core_ssh
20-11-29 07:29:57 ERROR (MainThread) [supervisor.utils] Can't execute update while a task is in progress
20-11-29 07:30:04 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.118.4 -> 404 Client Error: Not Found ("no such image: homeassistant/qemux86-64-homeassistant:0.118.4: No such image: homeassistant/qemux86-64-homeassistant:0.118.4").
20-11-29 07:30:04 INFO (SyncWorker_4) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 306.3 GiB
20-11-29 07:30:04 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
20-11-29 07:30:04 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-276' coro=<process_lock.<locals>.wrap_api() done, defined at /usr/src/supervisor/supervisor/utils/__init__.py:23> exception=HomeAssistantUpdateError()>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/utils/__init__.py", line 32, in wrap_api
return await method(api, *args, **kwargs)
File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 217, in update
raise HomeAssistantUpdateError()
supervisor.exceptions.HomeAssistantUpdateError
and
20-11-29 07:30:13 INFO (MainThread) [supervisor.api.security] /core/update access from core_ssh
20-11-29 07:30:13 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 0.118.4
20-11-29 07:30:13 INFO (SyncWorker_2) [supervisor.docker.interface] Updating image homeassistant/qemux86-64-homeassistant:0.118.0 to homeassistant/qemux86-64-homeassistant:0.118.4
20-11-29 07:30:13 INFO (SyncWorker_2) [supervisor.docker.interface] Downloading docker image homeassistant/qemux86-64-homeassistant with tag 0.118.4.
20-11-29 07:30:28 ERROR (SyncWorker_2) [supervisor.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.118.4 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").
20-11-29 07:30:28 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Needless to say: I can also ping the outside world from all containers and host.
EDIT: manually running “sudo docker pull homeassistant/qemux86-homeassistant” from within the host gives the same error"
EDIT2: after some research I found out it was my DNS. Fixed it by changing the DNS in /etc/resolv.conf to 8.8.8.8
Was it 1.1.1.1 before!? I noticed last week some sites via 1.1.1.1 were not resolving anymore. Changing to 8.8.8.8 immediately solved my problem. There must be something wrong with 1.1.1.1 now and then.