That will only get you working temporarily,
Soon after you’d notice that it is back to being problematic.
Thank you, that approach is much easier and quicker then a full update / reboot
What I don’t get is that I had docker in Ubuntu method working for very long time and very steadily, and all of a sudden with some Supervisor upgrade this problem started happening, and on every Home Assistant Update or on every Add-on update I have to do this dance to get it working.
I get it, it is not officially supported, but as seen in this thread and many others, lots of people are using this setup.
Why intentionally break it?
If a reboot fixes it, or if a supervisor restart fixes it, it is obvious that at some point after the restart, supervisor is running some script process to check things out and declaring it to be unsupported, effectively blocking updates.
Seeing that people have no choice but to restart the system or supervisor to proceed, and are doing so, why not add a configuration option to allow ignoring this unsupported flag and proceed regardless? Put a big warning if you want to discourage people, but forcing people to find workarounds and loopholes is not the best deterrent.
I have one system, which is an Ubuntu system, it is powerful and runs many other services aside from Dockerized Home Assistant, asking us to switch to Debian where this setup has been working for a very long time is unrealistic.
I’m not asking for it to be officially supported, what I’m asking is for it not to be intentionally handicapped.