Home Assistant Docker Container failed to start with Docker Engine 28.1.1

[PatrickHsu36]

Hello HA teams,
Once the Docker Engine is upgraded from 27.1.1 to 28.1.1, and the runc in docker engine is also upgraded from 1.1.13 to 1.2.6, and the latest home assistant docker container will fail to run in the same environment. The only different configuration is the Docker engine upgraded.

Does anyone can help on this?
Much appreciate !!

The error message is as the following:
docker start Home-Assistant

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: chmod /dev/console: read-only file system: unknown
Error: failed to start containers: Home-Assistant

[ThePotard]

It’s really a problem.
HA container did not work anymore on asustor NAS using last docker engine provided by Asustor…
Same error message
Help needed
Thanks in advance

[sigvind]

Home Assistant can no longer be called after Asustor update

I had the same problem after updating to 5.0.0.RHJ2. In my case helped doing the following: Using Portrainer CE for Home-Assistant container change access rights for Bind “/dev” from Read-Only to Writable. To do so, open container details (click on container), then edit container using Dublicate/Edit button and at Advanced container settings (volumes tab) change access rights for “/dev” from Read-Only to Writable. Then deploy container with replacement. After that container should immediately…

This one helped me in same situation. Don’t know if its a fix without side-effects, or a work-around.

[PatrickHsu36]

The issue is fixed by change the device path.