DSGW-230 - Home Assistant Supervised installation error

During the installation of Home Assistant Supervised I got the following error:

root@DUSUN:~# apt install ./homeassistant-supervised.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'homeassistant-supervised' instead of './homeassistant-supervised.deb'
The following additional packages will be installed:
  cifs-utils libtalloc2 libwbclient0
Suggested packages:
  smbclient winbind bash-completion
The following NEW packages will be installed:
  cifs-utils homeassistant-supervised libtalloc2 libwbclient0
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 169 kB/176 kB of archives.
After this operation, 904 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 /root/homeassistant-supervised.deb homeassistant-supervised all 1.7.0 [7428 B]
Get:2 http://deb.debian.org/debian bookworm/main arm64 libtalloc2 arm64 2.4.0-f2 [24.3 kB]
Get:3 http://deb.debian.org/debian bookworm/main arm64 libwbclient0 arm64 2:4.17.12+dfsg-0+deb12u1 [52.8 kB]
Get:4 http://deb.debian.org/debian bookworm/main arm64 cifs-utils arm64 2:7.0-2 [91.9 kB]
Fetched 169 kB in 1s (272 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libtalloc2:arm64.
(Reading database ... 97660 files and directories currently installed.)
Preparing to unpack .../libtalloc2_2.4.0-f2_arm64.deb ...
Unpacking libtalloc2:arm64 (2.4.0-f2) ...
Selecting previously unselected package libwbclient0:arm64.
Preparing to unpack .../libwbclient0_2%3a4.17.12+dfsg-0+deb12u1_arm64.deb ...
Unpacking libwbclient0:arm64 (2:4.17.12+dfsg-0+deb12u1) ...
Selecting previously unselected package cifs-utils.
Preparing to unpack .../cifs-utils_2%3a7.0-2_arm64.deb ...
Unpacking cifs-utils (2:7.0-2) ...
Selecting previously unselected package homeassistant-supervised.
Preparing to unpack .../homeassistant-supervised.deb ...
[warn] If you want more control over your own system, run
[warn] Home Assistant as a VM or run Home Assistant Core
[warn] via a Docker container.
Adding 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised'
Adding 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant-supervised'
Adding 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised'
Adding 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised'
Leaving 'diversion of /etc/systemd/resolved.conf to /etc/systemd/resolved.conf.real by homeassistant-supervised'
Unpacking homeassistant-supervised (1.7.0) ...
Setting up libwbclient0:arm64 (2:4.17.12+dfsg-0+deb12u1) ...
Setting up libtalloc2:arm64 (2.4.0-f2) ...
Setting up cifs-utils (2:7.0-2) ...
update-alternatives: using /usr/lib/aarch64-linux-gnu/cifs-utils/idmapwb.so to provide /etc/cifs-utils/idmap-plugin (idmap-plugin) in auto mode
Setting up homeassistant-supervised (1.7.0) ...
[info] Reload systemd
[info] Restarting NetworkManager
[info] Enable systemd-resolved
[info] Restarting systemd-resolved
[info] Set up systemd-journal-gatewayd socket file
[info] Enable systemd-journal-gatewayd
[info] Start nfs-utils.service
[info] Restarting docker service
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
dpkg: error processing package homeassistant-supervised (--configure):
 installed homeassistant-supervised package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+deb12u4) ...
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)


Docker status log:


root@DUSUN:~# systemctl status docker.service
× docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sat 2024-03-09 10:04:48 UTC; 40s ago
   Duration: 5min 13.806s
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
    Process: 2748 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 2748 (code=exited, status=1/FAILURE)

Can you please help to resolve it?