supervisor: Unable to update to supervisor / 404 Client Error: Not Found

The problem

Unable to update Supervisor to version 200

Environment

HASSIO

  • Home Assistant release with the issue: 0.105.x
  • Last working Home Assistant release (if known): n.a.
  • Operating environment (Hass.io/Docker/Windows/etc.): HASSIO

Problem-relevant configuration.yaml

n.a.

Traceback/Error logs

from logs:

Can't install homeassistant/armv7-hassio-supervisor:200 -> 404 Client Error: Not Found ("no such image: homeassistant/armv7-hassio-supervisor:200: No such image: homeassistant/armv7-hassio-supervisor:200").

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 40 (9 by maintainers)

Most upvoted comments

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Bad bot.

If this is indeed a disk space issue, perhaps a more descriptive error message (both on the supervisor updater GUI and logs) would be useful? 404 seems to indicate dockerhub connectivity issues

We agree, there is an issue open for that, however, it is the documented behavior by Docker as well (which is throwing this error message).

same problem here. cannot update. hassio updates normally.

df -h shows:

Filesystem                Size      Used Available Use% Mounted on
overlay                   6.6G      2.5G      3.7G  40% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                   462.0M         0    462.0M   0% /sys/fs/cgroup
shm                      64.0M     64.0K     63.9M   0% /dev/shm
/dev/root                93.8M     93.8M         0 100% /sbin/docker-init
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /config
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /share
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /addons
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /backup
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /data
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /ssl
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /etc/asound.conf
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /etc/hostname
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /etc/resolv.conf
/dev/mmcblk0p8            6.6G      2.5G      3.7G  40% /etc/hosts
tmpfs                   462.0M    608.0K    461.4M   0% /run/dbus
tmpfs                   462.0M         0    462.0M   0% /proc/asound
tmpfs                    64.0M         0     64.0M   0% /proc/keys
tmpfs                    64.0M         0     64.0M   0% /proc/latency_stats
tmpfs                    64.0M         0     64.0M   0% /proc/timer_list
tmpfs                    64.0M         0     64.0M   0% /proc/sched_debug
tmpfs                   462.0M         0    462.0M   0% /sys/firmware

This is going to sound weird (and we should improve on this), however, a 404 usually means there is not enough disk space available to complete the operation.