Can you reach this website from your browser?:
yep … sure can
[core-ssh ~]$ cd /tmp/
[core-ssh tmp]$ ls -la
total 12
drwxrwxrwt 1 root root 4096 Mar 28 11:39 .
drwxr-xr-x 1 root root 4096 Mar 28 11:39 ..
drwxr-xr-x 2 root root 4096 Mar 28 11:39 .bashio
[core-ssh tmp]$ wget https://github.com/home-assistant/core/pkgs/container/generic-x86-64-homeassistant
Connecting to github.com (20.248.137.48:443)
saving to 'generic-x86-64-homeassistant'
generic-x86-64-homea 100% |******************************************************************************************************| 173k 0:00:00 ETA
'generic-x86-64-homeassistant' saved
[core-ssh tmp]$ cat generic-x86-64-homeassistant
<!DOCTYPE html>
<html
lang="en"
data-color-mode="auto" data-light-theme="light" data-dark-theme="dark"
data-a11y-animated-images="system" data-a11y-link-underlines="true"
>........ etc etc etc :)
How much free disk space do you have ?
Same issue. Filed a bug on this and a separate post.
This has been coming up a great deal and is not an isolated issue. It needs to get fixed.
I used the Generic x86-64 - Home Assistant to do the install.
HA is installed in a proxmox VM
This is my disk usage
[core-ssh ~]$ df -h | grep -v tmpfs
Filesystem Size Used Available Use% Mounted on
overlay 7.2G 5.6G 1.3G 81% /
/dev/sda8 7.2G 5.6G 1.3G 81% /addons
/dev/sda8 7.2G 5.6G 1.3G 81% /backup
/dev/sda8 7.2G 5.6G 1.3G 81% /media
/dev/sda8 7.2G 5.6G 1.3G 81% /ssl
/dev/sda8 7.2G 5.6G 1.3G 81% /homeassistant
/dev/sda8 7.2G 5.6G 1.3G 81% /share
/dev/sda8 7.2G 5.6G 1.3G 81% /data
/dev/sda8 7.2G 5.6G 1.3G 81% /addon_configs
/dev/sda8 7.2G 5.6G 1.3G 81% /etc/asound.conf
/dev/sda8 7.2G 5.6G 1.3G 81% /run/audio
/dev/sda8 7.2G 5.6G 1.3G 81% /etc/resolv.conf
/dev/sda8 7.2G 5.6G 1.3G 81% /etc/hostname
/dev/sda8 7.2G 5.6G 1.3G 81% /etc/hosts
/dev/sda8 7.2G 5.6G 1.3G 81% /etc/pulse/client.conf
From within Home Assistant, what are the network settings? Settings > System > Network
Histname: homeassistant
Dhcp
Custom url that work from inaide and out
for the purposes of testing, I have just changed to a static ip.
no difference (and I didn’t expect there to be, it’s not my network, I run my own ISP 
)
2024-03-30 07:54:40.264 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.3.3: 404 Client Error for http+docker://localhost/v1.43/images/ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.3.3/json: Not Found ("No such image: ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.3.3")
2024-03-30 07:54:40.264 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
Sorry, I thought it was a network or docker network issue based on the error. The only other idea I have is that the image is not making it to the target location for the update to proceed. I’m not sure where to go from here.
It is a VM, so open the console and enter
docker pull ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.3.3
What error do you get?
1 Like
ah … @francisp that put me onto to something.
It was a disk space issue (although that was never clearly reported by the logs)
I’ve added another 10gb to the disk and it immediately updates.
The problem is probably specific to hypervisor users … if I had installed HAOS onto a real drive it would’ve been bigger to start with.
Thanks for all for trying to help 
Beyond francisp’s suggestion being spot on, what makes you think that 7.2G is sufficient disk space?
Unless I’m not remembering correctly, even a raspberry installation comes with the recommendation to use a 32gb card. Do yourself a favour and bump up that space even further while everything’s fresh in your mind
I was made to think that 7.2gb would be enough, because the instructions say the image is “6.4gb when decompressed”
I’m a 50 year old system admin, I’ve been at this system admin thing a VERY long time, and just about every iso/vmdk/raw image that is distributed in the FOSS world is distributed with an image size that will run the product.
And IF the image needs to be resized to support extra data, the company/people/clan tend to give instructions on this.
Nowhere in the instructions does it say “maybe resize your disks”
Thanks to help of @francisp I found my problem.
But yes, I did my self a favour and gave myself some extra disk space.
2 Likes
They do make the minimum requirements pretty clear in the installation page.
Glad you got everything sorted now.
An upgrade first pulls the docker upgrade (compressed), uncompresses it, switches to the new docker image, and if no startup problems then deletes the old docker image. So yes, quite some space needed for an upgrade.
1 Like
How much free disk space do you have ?
From within HAOS (OS 05 11.1, core 2024 3.3) what terminal command would you need to use to determine if you had enough space, and what should you be looking for in order to confirm whether you had enough?
I’d normally just use fdisk -l but it just dumps me back to the prompt without any visible output.
My install is on an SSD with over 100 gig on it, but I’m that doesn’t necessarily mean that there’s enough space in the relevant partition.
Command df give me this.
I’m running remotely and can’t copy\paste text right now (Problem for another thread), so everything has to be a screen shot.
This worked for me after a week digging! Thank you!