HA ERR_CONNECTION_REFUSED after update to the last version

Hi. I have a problem after updating to the last version
The HA has ** ERR_CONNECTION_REFUSED**

I have a version with the docker and hassio_supervisor

I checked the logs of hassio_supervisor and this is interesting:

23-06-28 21:32:42 ERROR (SyncWorker_4) [supervisor.docker.manager] 
Can't create container from homeassistant: 400 Client Error for http+docker://localhost/v1.41/containers/create?name=homeassistant: 
Bad Request ("invalid mount config: must use either propagation mode "rslave" or "rshared" when mount source is within the daemon root, daemon root: "/home/user/docker", bind mount source: "/home/user/docker/hassio/share", propagation: "slave"")

Did you ever have the same issue?

Some info:

  • Docker Root Dir: /home/user/docker
  • system: debian 11

Another log from the supervisor

23-06-28 21:58:54 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-1595' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:989> exception=AddonsJobError('Rate limit exceeded, more then 10 calls in 0:30:00')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 1003, in watchdog_container
    await self._restart_after_problem(self, event.state)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 144, in wrapper
    raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more then 10 calls in 0:30:00
23-06-28 22:02:27 INFO (SyncWorker_5) [supervisor.docker.manager] Runing command 'python3 -m homeassistant -c /config --script check_config' on ghcr.io/home-assistant/intel-nuc-homeassistant
23-06-28 22:03:21 ERROR (MainThread) [supervisor.homeassistant.core] Invalid Home Assistant config found!

when I used
docker exec -it hassio_cli bash and run ho core check there was information about the invalid configuration

How to check the configuration from cli or inside the docker?
I didn’t check anything before run update.

In general I assume that the container with the name homeassistant should be available. But cannot be created because Bad Request - how to solve that? Is it my corner case?