supervisor: hassio-supervisor fails to start and attach to an not running hassio_supervisor

Describe the issue you are experiencing

hassio-supervisor fails to start and attach to an already created but not runing hassio_supervisor

On an ordinary reboot, I find that hassio_supervisor never restart correctly, and I cannot start with systemctl start hassio-supervisor.service

It looks like the /usr/sbin/hassio-supervisor is hanging on the docker start --attach hassio_supervisor.

I am running docker version

Docker version 20.10.4

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

What is the used version of the Supervisor?

supervisor-2021.02.11

What type of installation are you running?

Home Assistant Supervised

Which operating system are you running on?

Debian

What is the version of your installed operating system?

Debian GNU/Linux 10 (buster)

What version of Home Assistant Core is installed?

core-2021.2.3

Steps to reproduce the issue

Try and reboot with an updated debian system and notice the supervisor doesn’t come back up.

docker rm -f hassio_supervisor, allows it come back up correctly.

Anything in the Supervisor logs that might be useful for us?

# Put your logs below this line

Nothing to log.

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 5
Comments: 32

Links to this issue

Warning: New docker killed HA supervised

Most upvoted comments

another temporary solution by holding back the upgrade by issuing this command:

sudo apt-mark hold docker-ce
sudo apt-mark hold docker-ce-cli

to cancel the hold when it’s safe to upgrade.

sudo apt-mark unhold docker-ce
sudo apt-mark unhold docker-ce-cli

Editted for typos

firestrife23 on Mar 4, 2021

Upgrading to docker-ce to 20.10.5 seems to fix the issue…

mamrai1 on Mar 3, 2021

Workaround: By downgrading docker-ce and cli HA supervised starts again.

remyderuysscher on Feb 28, 2021

sounds similar to this issue in Docker engine repo https://github.com/moby/moby/issues/42093#issuecomment-787100537

jhampson-dbre on Feb 28, 2021

Think its similar to this. https://github.com/home-assistant/supervisor/issues/1529 but no resolution there. I was able to get everything to work as expected commenting out the first or of the || statement

# Run supervisor
mkdir -p "${HASSIO_DATA}"
# ([ "${HASSIO_IMAGE_ID}" = "${HASSIO_CONTAINER_ID}" ] && docker start --attach hassio_supervisor) || 
runSupervisor

vajonam on Feb 27, 2021

For Ubuntu Server on Pi this worked for me

Find your specific docker version using apt-cache madison docker-ce

Then downgrade using

sudo apt-get install docker-ce=5:20.10.3~3-0~ubuntu-focal containerd.io sudo apt-get install docker-ce-cli=5:20.10.3~3-0~ubuntu-focal containerd.io sudo apt-get install docker-ce-rootless-extras=5:20.10.3~3-0~ubuntu-focal containerd.io sudo reboot

everything running smoothly again.

ads1230 on Mar 2, 2021

I also downgrade one more docker component and now every thing is fine.

sudo apt install docker-ce=5:20.10.3~3-0~raspbian-buster
sudo apt install docker-ce-cli=5:20.10.3~3-0~raspbian-buster
sudo apt install docker-ce-rootless-extras=5:20.10.3~3-0~raspbian-buster

sheminasalam on Mar 2, 2021

How about issuing alert as it was done with previous docker issue @pvizeli ?

andriej on Feb 28, 2021

did this break with Docker 20.10.4? I haven’t had any problem on 20.10.3.

jhampson-dbre on Feb 28, 2021