HA Supervisor Failed setup: troubles with Docker 25 upgrade. Supervisor unable to start #4827

GitWally · 2024-01-19T17:28:45Z

Describe the issue you are experiencing

Today MY HA went crazy, probably after a Debian OS update: it all started after an OS reboot.

From Settings > Integrations I see "Home Assistant Supervisor Failed setup, will retry"

Several other integrations same behaviour, some other are working (Shelly, MQTT, ZHA, HomeKit ...)

From HA Core Logs I see (among others):

Logger: homeassistant.helpers.system_info
Source: helpers/system_info.py:72
First occurred: 18:12:57 (1 occurrences)
Last logged: 18:12:57

No Home Assistant Supervisor info available

Logger: homeassistant.components.hassio
Source: components/hassio/__init__.py:557
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 18:02:11 (4 occurrences)
Last logged: 18:17:21

Can't read Supervisor data:

If I try to read HA Supervisor Logs: Failed to get supervisor logs, 502: Bad Gateway

What could be happend?

In Debian I found this updates to Docker Packages, today (with command cat /var/log/apt/history.log):

Start-Date: 2024-01-19  17:14:36
Commandline: packagekit role='update-packages'
Upgrade: docker-compose-plugin:amd64 (2.21.0-1~debian.11~bullseye, 2.24.1-1~debian.11~bullseye), docker-ce-cli:amd64 (5:24.0.7-1~debian.11~bullseye, 5:25.0.0-1~debian.11~bullseye), docker-buildx-plugin:amd64 (0.11.2-1~debian.11~bullseye, 0.12.1-1~debian.11~bullseye), docker-ce:amd64 (5:24.0.7-1~debian.11~bullseye, 5:25.0.0-1~debian.11~bullseye), docker-ce-rootless-extras:amd64 (5:24.0.7-1~debian.11~bullseye, 5:25.0.0-1~debian.11~bullseye)
End-Date: 2024-01-19  17:14:49

It all began after a reboot I did one hour after Debian OS Updates.

Tried to reboot Debian and HA several times: no changes
Tried to go for a backup: not visible when I press the button

Thanks

What type of installation are you running?

Home Assistant Supervised

Which operating system are you running on?

Debian

Steps to reproduce the issue

...

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

not available

System Health information

not available

Supervisor diagnostics

cannot find download diagnostics

Additional information

No response

The text was updated successfully, but these errors were encountered:

churchofnoise · 2024-01-19T17:44:48Z

Was about to post a bug too, started on both my servers after updating docker-ce and containerd.io on a supervised install on Debian bookworm, running on an Intel nuc 8

Aegeontis · 2024-01-19T18:04:19Z

Same thing, tried to manually stop all docker containers, remove them (docker stop & docker rm) and reboot the host, no change.

bighead85 · 2024-01-19T18:10:30Z

just downgraded specific packages and now system restored. (using Ubuntu 22.04)

docker-ce=5:24.0.7-1
docker-ce-cli=5:24.0.7-1
docker-ce-rootless-extras=5:24.0.7-1
docker-buildx-plugin=0.11.2-1

davecoutts · 2024-01-19T18:11:41Z

I experienced the same issue today after docker was upgraded following an apt upgrade on debian bookworm.
docker-ce upgraded from version 5:24.0.7-1 to 5:25.0.0-1.

I had to revert to the previous version of docker and then reboot the machine to get HA working again.

sudo apt install \
docker-compose-plugin=2.21.0-1~debian.12~bookworm \
docker-ce-cli=5:24.0.7-1~debian.12~bookworm \
docker-buildx-plugin=0.11.2-1~debian.12~bookworm \
docker-ce=5:24.0.7-1~debian.12~bookworm \
docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm

sudo reboot

See the apt log file for the versions you can rollback to.
cat /var/log/apt/history.log

Update:
Please see a more detailed post from GitWally on rolling back and placing the docker packages in hold state until the issue with supervisor and docker version 25.0 is resolved.

This post from fetzerch indicates that the issue is caused by the removal of an ip feature in Docker 25. There are plans to add the feature back in a future Docker release.

There is a post on the issue at the Home Assistant Community board.

ms32035 · 2024-01-19T19:30:36Z

Just hit the same. Looks like a networking related issue:

24-01-19 19:14:30 ERROR (SyncWorker_6) [supervisor.docker.network] Can't link container to hassio-net: 500 Server Error for http+docker://localhost/v1.44/networks/b2ac70d68ce32bb362d52d421fc940935a3ffd61846bc12d43caeaf2f8392337/connect: Internal Server Error ("invalid endpoint settings:
no configured subnet or ip-range contain the IP address 172.30.32.6")

adrienmar16 · 2024-01-19T19:59:50Z

davecoutts commands for donwgrading the docker doesn't resolve the problem form me :(
still "echec of configuration for home assistant supervisor".
How to solve that? (debian 12)
ERRATUM It's IS OK NOW. (need to have done it twice)
Big Thanks to davecoutts

MattWestb · 2024-01-19T20:34:50Z

Armbian Ubuntu Jammy:

apt install docker-ce=5:24.0.7-1~ubuntu.22.04~jammy
apt install docker-ce-cli=5:24.0.7-1~ubuntu.22.04~jammy
apt install docker-compose-plugin=2.21.0-1~ubuntu.22.04~jammy

And all containers is getting network OK.

fcastilloec · 2024-01-19T20:41:04Z

I also suggest holding those packages (keeping them from upgrading), so you can still install other updates to your system without this issue happening again:

sudo apt-mark hold \
docker-buildx-plugin \
docker-ce-cli \
docker-ce \
docker-ce-rootless-extras \
docker-compose-plugin

keshabit · 2024-01-20T06:11:29Z

Same issue encountered after docker upgrade, fix with:
sudo apt install
docker-compose-plugin=2.21.0-1~~debian.12~~bookworm
docker-ce-cli=5:24.0.7-1~~debian.12~~bookworm
docker-buildx-plugin=0.11.2-1~~debian.12~~bookworm
docker-ce=5:24.0.7-1~~debian.12~~bookworm
docker-ce-rootless-extras=5:24.0.7-1~~debian.12~~bookworm

fireballhh · 2024-01-20T06:21:20Z

confirmed downgrading docker resolves the problem.

also debian bookworm for me:

sudo apt install \
docker-compose-plugin=2.21.0-1~debian.12~bookworm \
docker-ce-cli=5:24.0.7-1~debian.12~bookworm \
docker-buildx-plugin=0.11.2-1~debian.12~bookworm \
docker-ce=5:24.0.7-1~debian.12~bookworm \
docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm

It seems that the upgrade deletes the eth1 entry for the hassio_supervisor after downgrade it gets restored and looks like this:

ifconfig
eth0      Link encap:Ethernet  HWaddr xxxx
          inet addr:172.17.0.4  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:155 errors:0 dropped:0 overruns:0 frame:0
          TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:90068 (87.9 KiB)  TX bytes:24992 (24.4 KiB)

eth1      Link encap:Ethernet  HWaddr xxxxx
          inet addr:172.30.32.2  Bcast:172.30.33.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:470 errors:0 dropped:0 overruns:0 frame:0
          TX packets:413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:91212 (89.0 KiB)  TX bytes:117692 (114.9 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:28 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2580 (2.5 KiB)  TX bytes:2580 (2.5 KiB)

also i notice that the entrys for hassio_observer, hassio_dns, hassio_cli, hassio_supervisor and hassio_audio where missing afther the upgrade in the docker hassio network bridge. Instead there where only two entrys for addons with 172.30.33.x ip´s
Afther downgrade it looks like this:

docker network inspect hassio
[
    {
        "Name": "hassio",
        "Id": "xyz",
        "Created": "2023-08-13T11:58:49.763727544Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.30.32.0/23",
                    "IPRange": "172.30.33.0/24",
                    "Gateway": "172.30.32.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "xyz": {
                "Name": "hassio_observer",
                "EndpointID": "xyz",
                "MacAddress": "xyz",
                "IPv4Address": "172.30.32.6/23",
                "IPv6Address": ""
            },
            "xyz": {
                "Name": "hassio_dns",
                "EndpointID": "4e246f8d7bb5122c0e44e6eaaaa6b7e2bd29b58762e5cf9980a8e7b12e39e35c",
                "MacAddress": "xyz",
                "IPv4Address": "172.30.32.3/23",
                "IPv6Address": ""
            },
            "xyz": {
                "Name": "hassio_cli",
                "EndpointID": "xyz",
                "MacAddress": "xyz",
                "IPv4Address": "172.30.32.5/23",
                "IPv6Address": ""
            },
            "xyz": {
                "Name": "hassio_supervisor",
                "EndpointID": "xyz",
                "MacAddress": "xyz",
                "IPv4Address": "172.30.32.2/23",
                "IPv6Address": ""
            },
            "xyz": {
                "Name": "hassio_audio",
                "EndpointID": "xyz",
                "MacAddress": "xyz",
                "IPv4Address": "172.30.32.4/23",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.bridge.name": "hassio"
        },
        "Labels": {}
    }
]

mamrai1 · 2024-01-20T06:35:22Z

davecoutts commands for donwgrading the docker doesn't resolve the problem form me :( still "echec of configuration for home assistant supervisor". How to solve that? (debian 12) ERRATUM It's IS OK NOW. (need to have done it twice) Big Thanks to davecoutts

You have to reboot the server...I have only downgraded docker-ce package and fixed the issue

GitWally · 2024-01-20T07:10:02Z

Thanks to all for your contributions: it worked also for me!
let me summarize for those newbies (like me) who could find out to be in the same shoes.

1. Check apt log to see the most recet updates to docker
With command cat /var/log/apt/history.log you can read which old package version was upgraded: you must go back to that one.
Eg:

docker-compose-plugin:amd64 (**2.21.0-1~debian.11~bullseye**, 2.24.1-1~debian.11~bullseye),

means docker-compose-plugin package must be roled back to version 2.21.0-1~~debian.11~~bullseye with command:

sudo apt install docker-compose-plugin=2.21.0-1~debian.11~bullsey

2. Rollback to the previous version of Docker packages
This was my apt log:


Commandline: packagekit role='update-packages'
Upgrade: 
docker-compose-plugin:amd64 (2.21.0-1~debian.11~bullseye, 2.24.1-1~debian.11~bullseye), 
docker-ce-cli:amd64 (5:24.0.7-1~debian.11~bullseye, 5:25.0.0-1~debian.11~bullseye), 
docker-buildx-plugin:amd64 (0.11.2-1~debian.11~bullseye, 0.12.1-1~debian.11~bullseye), 
docker-ce:amd64 (5:24.0.7-1~debian.11~bullseye, 5:25.0.0-1~debian.11~bullseye), 
docker-ce-rootless-extras:amd64 (5:24.0.7-1~debian.11~bullseye, 5:25.0.0-1~debian.11~bullseye)

this was the rollback of the same packages:

sudo apt install \
docker-compose-plugin=2.21.0-1~debian.11~bullseye \
docker-ce-cli=5:24.0.7-1~debian.11~bullseye \
docker-buildx-plugin=0.11.2-1~debian.11~bullseye \
docker-ce=5:24.0.7-1~debian.11~bullseye \
docker-ce-rootless-extras=5:24.0.7-1~debian.11~bullseye

3. Prevent the same packages to upgrade in the short term
To avoid the same issue to happen, until a stable solution will be found I decided to prevent the same packages to upgrade, as suggested by fcastilloec

sudo apt-mark hold \
docker-compose-plugin \
docker-ce-cli \
docker-buildx-plugin \
docker-ce \
docker-ce-rootless-extras \

Anyhow I think this is a bug that should be solved: preventing Docker packages to upgrade is just a temporary workaround, in my humble opinion.
Many thanks to all once again!

tracid56 · 2024-01-20T08:34:24Z

apt install docker-ce=5:24.0.7-1~~ubuntu.22.04~~jammy
apt install docker-ce-cli=5:24.0.7-1~~ubuntu.22.04~~jammy
apt install docker-compose-plugin=2.21.0-1~~ubuntu.22.04~~jammy

I confirm also that it's work after the downgrade.
Just a quick timeline :

This morning; I have a notification to update to Core 2024.1.4
I take this opportunity to also update my distribution debian 12 : sudo apt-get update && sudo apt-get upgrade -y
Reboot
And HA not working, lot of ''' Client error on /refresh_updates request Cannot connect to host 172.30.32.2:80 ssl:default [Connect call failed ('172.30.32.2', 80)]'''
Apply the downgrade
Reboot
HA available !

dimkin-eu · 2024-01-20T09:23:58Z

I got the same issue yesterday ( and from posts from the internet - many others as well )
common thing - Debian + docker update to 25 makes the supervisor not to start
downgrading docker to 24 returns everything back

@GitWally can you confirm and edit the issue's description to make it easier to find?

Alien-hide · 2024-01-20T09:28:54Z

confirm that after downgrade docker package, Supervisor start normaly

meta11st87 · 2024-01-20T09:33:29Z

I run this:
sudo apt install docker-compose-plugin=2.21.0-1~debian.12~bookworm docker-ce-cli=5:24.0.7-1~debian.12~bookworm docker-buildx-plugin=0.11.2-1~debian.12~bookworm docker-ce=5:24.0.7-1~debian.12~bookworm docker-ce-rootless-extras=5:24.0.7-1~debian.12~bookworm

But in docker I see:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5f4f18c1dd6d ghcr.io/home-assistant/amd64-hassio-multicast:2023.06.2 '/init' Less than a second ago Up Less than a second hassio_multicast
34170ecfd7fa ghcr.io/home-assistant/amd64-hassio-audio:2023.12.0 '/init' Less than a second ago Up Less than a second hassio_audio
146ff459d0c5 ghcr.io/home-assistant/amd64-hassio-dns:2023.06.2 '/init' Less than a second ago Up Less than a second hassio_dns
6f1e98cbe20b ghcr.io/home-assistant/amd64-hassio-cli:2023.11.0 '/init' Less than a second ago Up Less than a second hassio_cli
3db30fb2a584 ghcr.io/home-assistant/qemux86-64-homeassistant:2024.1.3 '/init' 31 minutes ago Up 31 minutes homeassistant
7e0fb66fe2b8 zigbee2mqtt/zigbee2mqtt-amd64:1.35.1-1 '/sbin/tini -- /dock…' 33 minutes ago Up 33 minutes 0.0.0.0:8486- 8485/tcp, :::8486- 8485/tcp addon_8c77aaed_zigbe e2mqtt

And the supervisor does not see running z2m and other containers.

What could be the problem?

RahFael · 2024-01-20T09:45:02Z

I had the same problem here with Home Assistant running on a Raspberry Pi 4b with the Raspberry OS Bullseye.
I even did a clean install using Raspberry OS Bookworm, but it was no use, as I had already updated the system and installed this Docker Update.
It wasn't until I went back to an image from the beginning of January that I realized that the problem was this docker update.

Thanks for the comments and tips. I wish I had found this topic sooner, so I wouldn't have stressed about it and wouldn't have thrown my SSD on the floor.

ORi0N · 2024-01-20T09:48:45Z

I had the same problem here with Home Assistant running on a Raspberry Pi 4b with the Raspberry OS Bullseye. I even did a clean install using Raspberry OS Bookworm, but it was no use, as I had already updated the system and installed this Docker Update. It wasn't until I went back to an image from the beginning of January that I realized that the problem was this docker update.

Thanks for the comments and tips. I wish I had found this topic sooner, so I wouldn't have stressed about it and wouldn't have thrown my SSD on the floor.

. If it's any comfort. Same here. I was in the middle of reworking my entire network setup and I thought the problem was there. I completely rebuilt my system (>7h+) before I found out docker was the culprit >_>

druidamix · 2024-01-20T09:59:15Z

Same problem after upgrade docker. Using my thermostat manually...

l4n-socrates · 2024-01-20T10:41:41Z

Exact the same problem, after updated debdian. Thanks for the troubleshooting and solution

GitWally · 2024-01-20T11:06:18Z

I got the same issue yesterday ( and from posts from the internet - many others as well )
common thing - Debian + docker update to 25 makes the supervisor not to start
downgrading docker to 24 returns everything back

@GitWally can you confirm and edit the issue's description to make it easier to find?

Yes I confirm the cause being Docker upgrade.
Please suggest any other hint to put the issue title.

Trebor87 · 2024-01-20T11:10:33Z

You guys saved my life, spent all morning thinking it was a HA bug and re-install only to find this page

Running the downgrade worked

Many thanks

dimkin-eu · 2024-01-20T11:41:27Z

@GitWally Update to Docker 25 disables supervisor start?

davecoutts · 2024-01-24T11:57:42Z

I'm happy to report that my Home Assistant is operating without issue after upgrading to docker-ce 25.0.1 on debian 12 bookworm.
I had to reboot the machine after unholding the docker packages and running apt upgrade in order to gain access to the Home Assistant. As per the commands below.

sudo apt-mark unhold \
docker-ce \
docker-ce-cli \
docker-buildx-plugin \
docker-compose-plugin \
docker-ce-rootless-extras

sudo apt update
sudo apt upgrade

sudo reboot

d4v1dk0n7 · 2024-01-24T12:14:08Z

Updated to 25.0.1 on raspberry 4, all working fine.

MattWestb · 2024-01-24T12:44:53Z

looks like 25.X is braking InfluxDB then all my systems is getting this:

ERROR (influxdb) [homeassistant.components.influxdb] Cannot connect to InfluxDB due to '[Errno 30] Read-only file system'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible.

And no data is pushed to the InfluxDB server.
ZHA withg NCP and RCP and Thread looks working OK

dimkin-eu · 2024-01-24T14:06:05Z

@MattWestb try to drop influx container

MattWestb · 2024-01-24T15:01:21Z

Thanks @dimkin-eu but is was not helping still all InfluxDB sensors is not saved in the bucket.

yiweiyu32 · 2024-01-24T17:17:22Z

Updated docker packages on x86_64. All working fine. docker-ce version (5:25.0.1-1~~debian.12~~bookworm)

yiweiyu32 · 2024-01-24T17:21:26Z

Debian Bookworm here as well.... you guys rock. Saved my install. Thanks!

Same story here. Almost started wiping the system and doing fresh install when found this thread. Downgrade helped well.

One question: why is this bug marked as "unsupported"?

Is supervised installation not one of the official ways to host HA? According to official docs my system is perfectly supported, and I just did my regular system update (what is also my "responsibility" according to the docs).

It's unsupported in the sense that "It's not the hass team's fault. Someone else messed up their updates. Go hound the Moby people for a fix."

fireashes · 2024-01-24T17:40:52Z

Updated to the following after unhold

sudo apt update

sudo apt list --upgradable

docker-buildx-plugin/bookworm 0.12.1-1~debian.12~bookworm amd64 [upgradable from: 0.11.2-1~debian.12~bookworm]
docker-ce-cli/bookworm 5:25.0.1-1~debian.12~bookworm amd64 [upgradable from: 5:24.0.7-1~debian.12~bookworm]
docker-ce-rootless-extras/bookworm 5:25.0.1-1~debian.12~bookworm amd64 [upgradable from: 5:24.0.7-1~debian.12~bookworm]
docker-ce/bookworm 5:25.0.1-1~debian.12~bookworm amd64 [upgradable from: 5:24.0.7-1~debian.12~bookworm]
docker-compose-plugin/bookworm 2.24.2-1~debian.12~bookworm amd64 [upgradable from: 2.21.0-1~debian.12~bookworm]

sudo apt-mark unhold \
docker-compose-plugin \
docker-ce-cli \
docker-buildx-plugin \
docker-ce \
docker-ce-rootless-extras

apt upgrade -y && apt install -f

Worked flawlessly after reboot of the machine

davecoutts · 2024-01-24T19:27:41Z

looks like 25.X is braking InfluxDB then all my systems is getting this:
ERROR (influxdb) [homeassistant.components.influxdb] Cannot connect to InfluxDB due to '[Errno 30] Read-only file system'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible.
And no data is pushed to the InfluxDB server. ZHA withg NCP and RCP and Thread looks working OK

@MattWestb did you manage to resolve the InfluxDB issue?

I have notice the same issue with the same error message.
The '[Errno 30] Read-only file system' error message appears to be coming from the a raised OSError here

My InfluxDB instance is on a different server that has not changed, so its something at the HA server end.
If I fall back to docker-ce 24.0.7 on the HA server the connection between HA and InfluxDB starts working again and no error is seen in the HA logs.

I wonder if it relates to moby/issues/47158 and the mounting behavior change in v25.
The influxdb python client makes use of multiprocessing, which the moby issue states is impacted by the change in permissions of /dev/shm

I'm speculating but its possible other modules that use multiprocessing in HA are impacted by docker-ce v25 and its change in mounting behavior.

MattWestb · 2024-01-24T19:57:51Z

I was updating 3 test systems and all was doing the same and i was rebootiong one before doing it and it was not having the error. And i was also rolling the production system then i is having more important things things that need the fix on it and loosing all sensor history.
The server is one Lubuntu AMD64 running docker containers and is not changed and is not giving anythings in the logs and the container is made of one portainer stack:

services:
  influxdb2:
    container_name: influxdb2
    image: influxdb:latest
    restart: unless-stopped
    ports:
      - '8086:8086'
    environment:
      - TZ=Europe/Vienna
    volumes:
      - /volume1/influxdb2:/var/lib/influxdb2
      - /etc/influxdb2:/etc/influxdb2

And the version is 2.7.3.
Reading the code you pointing at its one connection error that HA is logging as read error (its not completely false but better saying cant connection error).
So more then likely somthing is going wrong in the network connection and HA is not doing all OK with the in Docker 25.01.

davecoutts · 2024-01-24T20:20:39Z

I intend to raise a new issue in core for the docker-ce 25.0.x InfluxDB connectivity issue 1 2. This issue has tracked what was a docker problem, not a supervisor problem, for long enough.

gulliver103 · 2024-01-24T20:28:05Z

All good
Debian 11 Raspberry pi 4
Home Assistant observer
Supervisor: | Connected
Supported: | Supported
Healthy: | Healthy

sudo apt update

sudo apt-mark unhold \
docker-compose-plugin \
docker-ce-cli \
docker-buildx-plugin \
docker-ce \
docker-ce-rootless-extras

apt upgrade -y && apt install -f

sudo apt-cache policy docker-ce docker-ce-cli docker-ce-rootless-extras
docker-ce:
Installed: 5:25.0.1-1~~debian.11~~bullseye
Candidate: 5:25.0.1-1~~debian.11~~bullseye

MattWestb · 2024-01-24T20:31:06Z

Thanks @davecoutts !!
I was putting core and influxdb in full debug on one test system and nothing more interesting was coming in the HA log.
Im very likely going abroad on Friday and being away for one week so cant testing more but then im at home i can doing more testing if needed for fixing the issue.

davecoutts · 2024-01-24T21:26:51Z

Thanks @MattWestb

For anybody experiencing InfluxDB Integration failures following the update to docker-ce 25.0.1, I have raised an issue in core, core/issues/108810

xdedek · 2024-01-25T12:31:37Z

Hello at all... I have the same error in my HA on Debian 12 bookworm on a nuc....

In the observer I have this logs error :
Supervisor disconnected

24-01-19 15:27:50 CRITICAL (MainThread) [supervisor.supervisor] Can't setup Supervisor Docker container!
Many addons are out...

I am not a geek of the HA system but I have understand the problem is an update of docker CE....

But I am frenchee and use google to translate.... Could you explain properly to me the commands to pass (under putty ??) for to downgrade docker CE ?

Thanks

I wrote a comment at the end of the post for your case (debian12): #4827 (comment)

titou4307 · 2024-01-25T13:08:17Z

@xdedek
I have follow all the process and all was OK now

I am waiting the new update docker now

agners · 2024-02-01T15:29:07Z

This issue was caused by a bug in upstream Docker 25.0.0. As mentioned in #4827 (comment), 25.0.1 fixed this problem. I am closing the issue as there is nothing to be done on Supervisor side.

Thanks for reporting and help getting to the bottom of this!

damiano75 · 2024-02-06T07:24:29Z

Upgrading to Supervisor 2024.01.1 needs to rollback again...

titou4307 · 2024-02-06T07:31:21Z

I have update the Supervisor to the last version....But I have not done the update Docker (blocked)
no problem but it not a solution to the long time....

agners · 2024-02-06T07:38:26Z

Upgrading to Supervisor 2024.01.1 needs to rollback again...

If you see an issue with 2024.01.1 please open a new issue along with logs. It is most likely unrelated to this particular issue as this was about Docker causing issues.

akunia · 2024-02-21T08:31:45Z

Hi,
Anybody can give me the commands to upgrade to Docker version 25.0.3 ?
I have again unhealthy message on Docker version 24.0.7

Datortarp5 · 2024-02-21T09:49:24Z

Hi, Anybody can give me the commands to upgrade to Docker version 25.0.3 ? I have again unhealthy message on Docker version 24.0.7

sudo apt update
sudo apt upgrade docker

akunia · 2024-02-21T09:56:06Z

Hi, Anybody can give me the commands to upgrade to Docker version 25.0.3 ? I have again unhealthy message on Docker version 24.0.7

sudo apt update sudo apt upgrade docker

Are you sure ??? Tis will not install 25.0.0.1 ?
It's wat's proposed to me:
hpbian@hpbian:~$ sudo apt-cache policy docker-ce docker-ce-cli docker-ce-rootless-extras [sudo] password for hpbian: docker-ce: Installed: 5:24.0.7-1~debian.12~bookworm Candidate: 5:25.0.0-1~debian.12~bookworm
EDIT: sorry, after apt update, i have 25.0.3. Thanks

titou4307 · 2024-02-23T09:06:20Z

Hi
Does it OK now with the last version Docket and HA ?

At this time time my docker version is "holded" so I need to unhold for have the update of this packet

Thanks

dtalens · 2024-02-23T09:14:45Z

Hi Does it OK now with the last version Docket and HA ?

At this time time my docker version is "holded" so I need to unhold for have the update of this packet

Thanks

It's working fine with Docker 25.0.3. If necessary you can restart supervisor after upgrade.

GitWally added the bug label Jan 19, 2024

dimkin-eu mentioned this issue Jan 20, 2024

Supervisor keeps going “Unhealthy” #4381

Closed

GitWally changed the title ~~HA Supervisor Failed setup, will retry: Failed to get supervisor logs, 502: Bad Gateway~~ HA Supervisor Failed setup: troubles with Docker upgrade Jan 20, 2024

mmattel mentioned this issue Jan 20, 2024

Upgrading the docker packages results in failing DNS container start #4828

Closed

GitWally changed the title ~~HA Supervisor Failed setup: troubles with Docker upgrade~~ HA Supervisor Failed setup: troubles with Docker 25 upgrade Jan 20, 2024

GitWally changed the title ~~HA Supervisor Failed setup: troubles with Docker 25 upgrade~~ HA Supervisor Failed setup: troubles with Docker 25 upgrade unable to start Jan 20, 2024

GitWally changed the title ~~HA Supervisor Failed setup: troubles with Docker 25 upgrade unable to start~~ HA Supervisor Failed setup: troubles with Docker 25 upgrade Supervisor unable to start Jan 20, 2024

donaldguy mentioned this issue Jan 26, 2024

supervisor running unconfined (w/o apparmor profile) after reboot THEN w/ insufficient perms to monitor udev after recreate #4839

Open

davecoutts mentioned this issue Jan 28, 2024

HA InfluxDB integration fails with Read-only file system error following upgrade to Docker 25.0.x home-assistant/core#108810

Closed

donaldguy mentioned this issue Jan 28, 2024

Bug Report/Feature-ish request: debian package should provide container runtime version constraint home-assistant/supervised-installer#355

Open

3 tasks

agners closed this as not planned Won't fix, can't repro, duplicate, stale Feb 1, 2024

github-actions bot locked and limited conversation to collaborators Mar 25, 2024

HA Supervisor Failed setup: troubles with Docker 25 upgrade. Supervisor unable to start #4827

HA Supervisor Failed setup: troubles with Docker 25 upgrade. Supervisor unable to start #4827

Comments

GitWally commented Jan 19, 2024 • edited

Describe the issue you are experiencing

What type of installation are you running?

Which operating system are you running on?

Steps to reproduce the issue

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

System Health information

Supervisor diagnostics

Additional information

churchofnoise commented Jan 19, 2024 • edited

Aegeontis commented Jan 19, 2024 • edited

bighead85 commented Jan 19, 2024 • edited

davecoutts commented Jan 19, 2024 • edited

ms32035 commented Jan 19, 2024

adrienmar16 commented Jan 19, 2024 • edited

MattWestb commented Jan 19, 2024

fcastilloec commented Jan 19, 2024

keshabit commented Jan 20, 2024

fireballhh commented Jan 20, 2024 • edited

mamrai1 commented Jan 20, 2024

GitWally commented Jan 20, 2024

tracid56 commented Jan 20, 2024 • edited

dimkin-eu commented Jan 20, 2024

Alien-hide commented Jan 20, 2024

meta11st87 commented Jan 20, 2024 • edited

RahFael commented Jan 20, 2024

ORi0N commented Jan 20, 2024

druidamix commented Jan 20, 2024 • edited

l4n-socrates commented Jan 20, 2024 • edited

GitWally commented Jan 20, 2024

Trebor87 commented Jan 20, 2024

dimkin-eu commented Jan 20, 2024

davecoutts commented Jan 24, 2024

d4v1dk0n7 commented Jan 24, 2024

MattWestb commented Jan 24, 2024

dimkin-eu commented Jan 24, 2024

MattWestb commented Jan 24, 2024

yiweiyu32 commented Jan 24, 2024

yiweiyu32 commented Jan 24, 2024 • edited

fireashes commented Jan 24, 2024 • edited

davecoutts commented Jan 24, 2024 • edited

MattWestb commented Jan 24, 2024

davecoutts commented Jan 24, 2024

gulliver103 commented Jan 24, 2024

MattWestb commented Jan 24, 2024

davecoutts commented Jan 24, 2024

xdedek commented Jan 25, 2024

titou4307 commented Jan 25, 2024

agners commented Feb 1, 2024

damiano75 commented Feb 6, 2024

titou4307 commented Feb 6, 2024

agners commented Feb 6, 2024

akunia commented Feb 21, 2024

Datortarp5 commented Feb 21, 2024

akunia commented Feb 21, 2024 • edited

titou4307 commented Feb 23, 2024

dtalens commented Feb 23, 2024

GitWally commented Jan 19, 2024 •

edited

churchofnoise commented Jan 19, 2024 •

edited

Aegeontis commented Jan 19, 2024 •

edited

bighead85 commented Jan 19, 2024 •

edited

davecoutts commented Jan 19, 2024 •

edited

adrienmar16 commented Jan 19, 2024 •

edited

fireballhh commented Jan 20, 2024 •

edited

tracid56 commented Jan 20, 2024 •

edited

meta11st87 commented Jan 20, 2024 •

edited

druidamix commented Jan 20, 2024 •

edited

l4n-socrates commented Jan 20, 2024 •

edited

yiweiyu32 commented Jan 24, 2024 •

edited

fireashes commented Jan 24, 2024 •

edited

davecoutts commented Jan 24, 2024 •

edited

akunia commented Feb 21, 2024 •

edited