HA Core update 2025.11.0 failing

Installation
1

2025.10.4 to 2025.11.0

It just runs then doesn’t work. Thsi is what I’m seeing in supervisor logs: (HAOS install straight on NUC with oodles of space)

2025-11-06 17:26:33.246 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-2034' coro=<DockerInterface.install.<locals>.process_pull_image_log() done, defined at /usr/src/supervisor/supervisor/docker/interface.py:404> exception=TypeError("unsupported operand type(s) for +=: 'int' and 'NoneType'")>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/docker/interface.py", line 406, in process_pull_image_log
    self._process_pull_image_log(curr_job_id, reference)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/docker/interface.py", line 345, in _process_pull_image_log
    total += job.extra["total"]
TypeError: unsupported operand type(s) for +=: 'int' and 'NoneType'
2025-11-06 17:26:33.256 ERROR (SyncWorker_2) [supervisor.docker.manager] failed to register layer: archive/tar: invalid tar header
2025-11-06 17:26:33.257 WARNING (MainThread) [supervisor.jobs] Removing incomplete job Pulling container image layer from job manager
2025-11-06 17:26:33.257 WARNING (MainThread) [supervisor.jobs] Removing incomplete job Pulling container image layer from job manager
2025-11-06 17:26:33.257 WARNING (MainThread) [supervisor.jobs] Removing incomplete job Pulling container image layer from job manager
2025-11-06 17:26:33.257 WARNING (MainThread) [supervisor.jobs] Removing incomplete job Pulling container image layer from job manager
2025-11-06 17:26:33.257 WARNING (MainThread) [supervisor.jobs] Removing incomplete job Pulling container image layer from job manager
2025-11-06 17:26:33.258 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
2025-11-06 17:27:49.046 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)"
2

Hello RogerD,

If you believe you have found a bug and your discussions here have people agreeing with you (It’s not currently working as designed) then you should check the issues. If it is working as designed and you just don’t like it, then look at the Feature Request Category for more info.
If there is already an issue for it, add a thumbs up to help push the effort along. If there is not an issue open for it open one.
It’s good to discuss and verify that there is an issue here, but if you want the appropriate developer to look at it & maybe get it resolved, it will have to be seen as an issue…

ISSUES
¯\(ツ)/¯ Sounds like you are looking for…

That is a general statement I have stored up here, but I have not heard reports of this yet. I am by no means an expert.

3

Update - got it to work by booting into safe mode. No idea why! can anyone point me to logs I should be inspecting. I find the whole log thing confising as there are many of them and I don’t always know where they are. Very happy to learn!

4

Corrupt tar? Network problems during update or disk data corruption?