Unhealthy - but Healthy: true?

Firstly let me acknowledge know the following is technnically “unsupported” but I’m aware of many of us in the community running similar setups so looking to share experiances and see if anyone can help solve my issue.

It’s a manually installed supervisor on docker system on Ubuntu 22.04.1

My setup has been running happily for several months, marked “unsupported” - but always “healthy” with the most recent update I installed being 2022.9.5

Docker is at 20.10.21 and I haven’t added any new containers.

I’m running following docker containers:

Now since early October it’s declared my installation “unhealthy” with the explaination “docker”.

I’ve checked and rechecked docker is bang up to date and as far as I can tell configured just the same as it’s always been, and in fact, as you’ll see below, after my most recent updates and reboot it clearly says in the system information: Healthy: true - but at the top it still shows Unhealthy and refuses to install updates.

Any suggestions to help diagnose the cause and discrepancy between Healthy: true and “Unhealthy” appearing on the same screen?!


System Information

version core-2022.9.5
installation_type Home Assistant Supervised
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.5
os_name Linux
os_version 5.15.0-52-generic
arch x86_64
timezone Europe/London
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4903
Installed Version 1.27.1
Stage running
Available Repositories 1131
Downloaded Repositories 5
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Ubuntu 22.04.1 LTS
update_channel stable
supervisor_version supervisor-2022.10.0
agent_version 1.2.2
docker_version 20.10.21
disk_total 467.3 GB
disk_used 45.1 GB
healthy true
supported failed to load: Unsupported
supervisor_api ok
version_api ok
installed_addons Studio Code Server (5.4.0), Mosquitto broker (6.1.3), Terminal & SSH (9.6.1), Samba share (10.0.0)
dashboards 1
resources 3
views 6
mode storage
oldest_recorder_run 21 October 2022 at 07:24
current_recorder_run 31 October 2022 at 15:59
estimated_db_size 356.04 MiB
database_engine sqlite
database_version 3.38.5

Maybe this?

1 Like

Thank you very much. Problem solved.

Foolishly as portainer had been acceptable for many months I didn’t think to check if it has become unacceptable. Since I don’t actually use portainer and put it on there on at the suggestion of a colleague to have a play I’ve simply removed the container, restarted and job done - system healthy again.