’
Can’t create container from addon_core_configurator: 409 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_core_configurator: Conflict (“Conflict. The container name “/addon_core_configurator” is already in use by container “a3e11681017e90cac39dff31975b9a37c0009c63d4f196bc637bbbf90a89f9bf”. You have to remove (or rename) that container to be able to reuse that name.”)
’
I have the same by the MQTT Broker, and by TasmoAdmin…, i do not know what to do…
Looks like you might have another docker container running of the same home assistant image. Perhaps an older one? You can do docker ps -a to see what containers are running. If you have more than one of your homeassistant container, kill the old one. docker kill <container ID>
Thanks for your hint.but I have used another way: I have made everything new. This needs a lot of time, but now some parts i have made by another way and i hope that now my HASS runs…
I don’t know exactly why this happens but I’ve seen it before as well. There seems to be some failure removing the docker container when the addon is stopped and it gets “stuck”. It’s not just an HA thing either, if you use the docker CLI to try and remove the “stuck” container you’ll get an error that is google-able. I found a lot of people encountering it.
The suggestion always seems to be “restart docker”. On an HAOS system that basically means reboot the host. On a supervised system you could probably try sshing in and restarting the docker service instead of rebooting the host if you prefer.
Rebooting the host has always fixed it for me when it’s appeared.