HAOS slow, some things not working, docker unresponsive

Installation
1

Hi,
since yesterday I have and issue with my home assistant that is running in a VM. Yesterday I first noticed when it was just incapable of updating supervisor. I started poking around and found out that docker commands are very unresponsive (tbh a lot was very slow but docker just didn’t respond to even a simple docker ps). I tried restarts it didn’t help. I see that my docker process is constantly using about 30 % of the processor capacity. I was unable to make or download any backups that I had. Luckily I had one backup in cloud, so I though that I will just recreate the VM from scratch and restore. But after restoring the issue continues. Even without installed apps (addons). I booted to safe mode and started installing the apps back and it takes ages. It succeeds but install and start it taking up to an hour. And when I tried to install new core it just told me that there was some timeout on gathering docker info:

[3732534159952] Error during service call to update.install: Error updating Home Assistant Core: Timeout occurred while getting container information for homeassistant

On the os there is a lots of:

2026-10-02 09:11:46.652 homeassistant dockerd[671]: time="2026-10-02T09:10:58.979009138Z" level=warning msg="Health check for container 548106e4e7245e8745e50f0504a5003c72964aa337fe26b57009e9d786074598 error: timed out starting health check for container 548106e4e7245e8745e50f0504a5003c72964aa337fe26b57009e9d786074598"

here are some exceptions from supervisor logs:

Summary 
2026-10-02 08:49:27.921 ERROR (MainThread) [supervisor.resolution.evaluations.container] Timeout while evaluating docker containers
2026-10-02 08:49:27.923 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-10-02 08:49:27.924 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2026-10-02 08:49:27.924 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2026-10-02 09:29:48.075 INFO (MainThread) [supervisor.host.info] Updating local host information
2026-10-02 09:29:53.308 INFO (MainThread) [supervisor.host.services] Updating service information
2026-10-02 09:29:53.415 INFO (MainThread) [supervisor.host.network] Updating local network information
2026-10-02 09:29:53.510 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-10073' coro=<Scheduler._run_task.<locals>._wrap_task() done, defined at /usr/src/supervisor/supervisor/misc/scheduler.py:57> exception=DockerTimeoutError('Timeout occurred while getting container information for homeassistant')>
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client_reqrep.py", line 558, in start
    message, payload = await protocol.read()  # type: ignore[union-attr]
                       ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/streams.py", line 705, in read
    await self._waiter
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/docker/interface.py", line 423, in _get_container
    return await self.sys_docker.containers.container(self.name).show()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiodocker/containers.py", line 278, in show
    data = await self.docker._query_json(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        f"containers/{self._id}/json", method="GET", params=kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiodocker/docker.py", line 556, in _query_json
    async with self._query(
               ~~~~~~~~~~~^
        path,
        ^^^^^
    ...<6 lines>...
        versioned_api=versioned_api,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ) as response:
    ^
  File "/usr/local/lib/python3.14/contextlib.py", line 214, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiodocker/docker.py", line 448, in _query
    yield await self._do_query(
          ^^^^^^^^^^^^^^^^^^^^^
    ...<9 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiodocker/docker.py", line 506, in _do_query
    response = await self.session.request(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<8 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 858, in _request
    resp = await handler(req)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 836, in _connect_and_send_request
    await resp.start(conn)
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client_reqrep.py", line 553, in start

Live

What should I do to troubleshoot next?
Thank you

Edit2: The issue is still persisting even without apps. Latest supervisor logs again point at docker hanging :confused:

2026-10-03 07:36:27.709 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2026-10-03 07:51:28.526 ERROR (MainThread) [supervisor.resolution.evaluations.container] Timeout while evaluating docker containers
2026-10-03 07:51:28.532 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-10-03 07:51:28.534 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2026-10-03 07:51:28.535 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2026-10-03 07:55:55.812 INFO (MainThread) [supervisor.host.info] Updating local host information
2026-10-03 07:55:57.108 INFO (MainThread) [supervisor.host.services] Updating service information
2026-10-03 07:55:57.233 INFO (MainThread) [supervisor.host.network] Updating local network information
2026-10-03 07:55:58.656 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2026-10-03 07:55:58.785 INFO (MainThread) [supervisor.host.manager] Host information reload completed
2026-10-03 08:02:48.541 WARNING (MainThread) [supervisor.misc.tasks] Watchdog missed an Home Assistant Core API response.
2026-10-03 08:09:30.541 INFO (MainThread) [supervisor.store.git] Update app /data/apps/git/5c53de3b repository from https://github.com/esphome/home-assistant-addon
2026-10-03 08:09:30.546 INFO (MainThread) [supervisor.store.git] Update app /data/apps/git/a0d7b954 repository from https://github.com/hassio-addons/repository
2026-10-03 08:09:30.546 INFO (MainThread) [supervisor.store.git] Update app /data/apps/core repository from https://github.com/home-assistant/addons
2026-10-03 08:09:30.547 INFO (MainThread) [supervisor.store.git] Update app /data/apps/git/d5369777 repository from https://github.com/music-assistant/home-assistant-addon
2026-10-03 08:09:34.175 INFO (MainThread) [supervisor.store] Loading apps from store: 96 all - 0 new - 0 remove
2026-10-03 08:51:28.551 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running

Edit3: I see that there were some docker related changes in the latest release so it may be an actual bug…

2

So you have HA running in a docker container in a virtual machine?
Are you sure that is what you want?

3

…

Those 2 statements contradict each other. Which one is correct?

4

So you have HA running in a docker container in a virtual machine?
Are you sure that is what you want?

It the default HAOS (KVM image), I didn’t change anything. As far as I know this is how the HAOS works - core is a docker container and addons are installed as other docker containers.

5

Its unfolding as the edits go. Turns out its not the whisper its something with docker, because I have no addons and the issue is back. And I see:

2026-10-03 07:51:28.526 ERROR (MainThread) [supervisor.resolution.evaluations.container] Timeout while evaluating docker containers

I updated the post so that it is not confusing. Sorry for the mess, I am troubleshooting as I go, but I honestly don’t know how to figure out what’s wrong.

6

If you are running container, IE Docker version there are no Apps. Add-ons are not even a thing anymore, name was changed.
If you are running HAOS it is a Docker container but completely controlled by HA and it will just work. If you are running Container, you have to have the knowledge to make it work yourself (That’s why it’s under advanced with the VM install as well), and know there are no Apps, and you have to use Dockers to get your App-like functions. You can look here as a good source: GitHub - awesome-selfhosted/awesome-selfhosted: A list of Free Software network services and web applications which can be hosted on your own servers · GitHub

So my concern is the questions you are asking were telling me that HAOS is likely a better fit for your current skill level. Nothing wrong with that, been running that many years myself. The experts control the back-end and you don’t have to care about it.

7

From where (or how) did you issue this command? This might not be an available command on HAOS.

Also can you describe your metal box & OS that runs your VM host? What else is on the metal box? What other VMs / containers are running on the metal box but not inside HAOS??

8

So my concern is the questions you are asking were telling me that HAOS is likely a better fit for your current skill level. Nothing wrong with that, been running that many years myself. The experts control the back-end and you don’t have to care about it.

Man, I don’t know what are you trying to tell me. I am running HAOS in a VM. That’s it. And that system (HAOS) is using docker (under-the-hood) whether I need to know that or not. And yes installing Apps/Add-on (whatever) is creating more containers. My point is that my system stopped working reliably and the troubleshooting led me inside (under the hood) and I noticed that docker is unresponsive.

9

From my VM shell.

I am running the VM on TrueNAS. Its standard x86 computer (AM4 generation of components).

I have actually downgraded HAOS to 18.2 and the issue is gone, so I reported the issue here - there you can see more details about the issue and the system, but as it stands now, I don’t think I can do more than to report it and hope for the fix.

10

There is no docker ps command in HAOS, and you cannot get one – apt-get is not a thing either. There is supervisor info and supervisor stats you can run from shell, but not the same.

SG is trying to see what kind of install you have - because you talked about docker ps (among other things) as if you have done so before in your install, and he also know there is no such thing as docker ps, so it is (or was) confusing… based on the initial information you have provided… hence this question trying to seek clarifications:

Now, you have since clarified that you are indeed running HAOS as a VM. Plus you have opened an issue… let’s see what people say about the issue.

11

image
image1240×795 158 KB

How do you explain this then?

You should really apologize to the OP and let this be a lesson not to be too sure of yourself.

12

I gave up on this one already.
The OP is clearly smarter than most of the rest of us…
I am sorry I tried to offer advice to you.

13

Sure. I am dumb and stand corrected.

14

There is no docker ps command in HAOS

I think I never said I ran docker ps inside HAOS. I was running the command in the VM shell that is running HAOS. I even clarified that later. I didn’t mean anything I wrote above to be rude and if it came of that way I sincerely apologize.

15

The OP is clearly smarter than most of the rest of us…

I was just confused, you were basically telling me that the way I am running it (HAOS) “it will just work” when it clearly was not, that’s why I tried to clarify, I didn’t want to be “smart” or anything and if I insulted you in any way, same as with k8gg, I sincerely apologize.

16

Thank you for standing up for me man :yellow_heart: