I run Debian 10.8 as host system and today I did apt-get upgrade and got containerd.io upgrade from 1.4.3-1 to 1.4.4-1). After the upgrade all my docker containers where stopped. So I rebooted the system and after that most of the containers where started and running correctly. Except all HomeAssisant en HassIO containers.
When I tried to start the HassIO supervisor manually it will stop after a few seconds. There’s no exception or something in the log:
21-03-12 17:26:18 INFO (MainThread) [__main__] Initializing Supervisor setup
21-03-12 17:26:18 INFO (MainThread) [supervisor.bootstrap] Initializing Supervisor Sentry
21-03-12 17:26:18 INFO (MainThread) [supervisor.bootstrap] Seting up coresys for machine: qemux86-64
21-03-12 17:26:18 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attaching to Supervisor homeassistant/amd64-hassio-supervisor with version 2021.03.4
21-03-12 17:26:18 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-03-12 17:26:18 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.INITIALIZE
21-03-12 17:26:18 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-03-12 17:26:18 INFO (MainThread) [__main__] Setting up Supervisor
21-03-12 17:26:18 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
21-03-12 17:26:18 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
I tried several things to start of fix the supervisor but with no succes. For example:
banaan@serverbanaan:/usr/share/hassio$ sudo ha supervisor reload
Error response from daemon: Container 12efbd04d805e11e0e80c1db1ed555299ef3529f132675ca1964c5db36d6cffd is not running
Anyone any suggestion how to get my system back online? I read several posts online that restoring a snapshot wont’t fix the problem, because the problem is at the host of the system.
I did’t such huge impact of containerd upgrade. I’ve checked my apt-get upgrade command and containerd was the only installed / upgraded package. And I checked sky logfiles from different containers and they stopped working around the time I upgraded containerd.
My host is running Docker version 20.10.5, build 55c4c88