Addons wont start

1

Versio core-2025.11.1

Host operating system Debian GNU/Linux 13 (trixie)
Update channel beta
Supervisor version supervisor-2025.11.2

Just updated docker and then reboot. Now addons wont start at all.
Any nice trick?

Well…
Trick is but not are fix.
When system reboot, then:
ha supervisor reload
ha supervisor restart

If system reboot again, auto start still not working

1 Like
2

I have exactly the same problem after upgrading the following packages:

containerd.io (1.7.29-1)
docker-ce-cli (5:28.5.2-1)
docker-ce (5:28.5.2-1)
docker-ce-rootless-extras (5:28.5.2-1)

I will try downgrading later today one by one which one is causing this.

1 Like
3

I have the same issue, also after the docker update. The trick from @habb0 worked for now, thank you for that!

4

It seems like some changes coming with the latest containerd.io 2.1.5-1 is breaking the loading of Add-Ons.

If on HA Supervised and Debian 12 (bookworm) you can easily downgrade:

Go to the CLI.

As root user do:

systemctl stop docker
apt remove docker-ce docker-ce-cli containerd.io
apt install docker-ce=5:28.5.2-1~debian.12~bookworm docker-ce-cli=5:28.5.2-1~debian.12~bookworm containerd.io=1.7.29-1~debian.12~bookworm

Now switch to the normal (unpriviledged) user HA is running with and then do:

sudo -i
cd /usr/local/src
mv homeassistant-supervised.deb homeassistant-supervised.deb.orig
wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb
dpkg -i homeassistant-supervised.deb

Reboot the host.

If you want to put any further upgrades to docker on hold until the issue has been sorted out just do from CLI:
sudo apt-mark hold docker-ce docker-ce-cli containerd.io

To unhold:
sudo apt-mark unhold docker-ce docker-ce-cli containerd.io

As for Debian 13 (trixie) look up the the last version (before latest) to downgrade to that version:

sudo apt-cache policy docker-ce
sudo apt-cache policy docker-ce-cli
sudo apt-cache policy containerd.io
3 Likes
5

Thanks worked like a charm

1 Like
6

For me issue persist with docker-ce 5:29, no need to upgrade yet.

1 Like
7

Or you could try:

apt reinstall docker-ce=5:28.5.2-1~debian.12~bookworm docker-ce-cli=5:28.5.2-1~debian.12~bookworm containerd.io=1.7.29-1~debian.12~bookworm

Then you won’t have to reinstall homeassistant-supervised.deb. At least it worked for me.

8

With the following versions everything is went back to normal for me:

containerd.io:
  Installed: 2.1.5-1~debian.13~trixie
docker-ce:
  Installed: 5:29.0.2-1~debian.13~trixie
docker-ce-cli:
  Installed: 5:29.0.2-1~debian.13~trixie
docker-ce-rootless-extras:
  Installed: 5:29.0.2-1~debian.13~trixie
1 Like
9

Thank you fort letting us know :hugs:

The same goes for the latest docker versions for Debian 12 bookworm:

If put on hold before just initiate from CLI:

sudo apt-mark unhold docker-ce docker-ce-cli containerd.io

Then run a normal system upgrade:

sudo apt update && sudo apt upgrade && sudo apt autoremove

which will upgrade the outdated docker versions to the latest.

Reboot the host and all will be back to normal again :+1:

1 Like