You don’t install the actual “add-on” with a docker install and would need to install/configure its equivalent. And that’s going to depend on which “add-on” you want.
The problem is you can’t really put together a comprehensive guide because the host OS and overall configuration is going to be very different from one Docker install to another. To get the added flexibility you have to trade off that it will be more complicated to manage.
This person has put together quite a few helpful guides, and would be a good place to start for setting up Home Assistant container -
My post above is old but still relevant for this. You can use the text editor in the host OS on the machine running Docker, you can setup a SAMBA share, and/or setup SSH to edit the file in host machine from another one.
If the host OS is Ubuntu here would be links on how to configure Samba and SSH- so you can edit files with either one. Once configured SAMBA is really nice because from any Windows machine on your network you just use the file explorer to go to you home assistant config on the Ubuntu machine and can edit it with notepad/wordpad.
https://ubuntu.com/tutorials/install-and-configure-samba#1-overview
There are other guides in this forum, such as how to configure SWAG - linuxserver/swag - Docker Image for secure remote access, and a guide I wrote up on how to install Wireguard in docker for a VPN - Wireguard Container
Zwave can be installed in docker by following these steps - scroll down to “Option 3 - The Z-Wave JS UI Docker container” - Z-Wave - Home Assistant
Zigbee2mqtt can be installed in docker following these steps - Docker | Zigbee2MQTT
An MQTT broker can be installed in docker following these steps - Configuring the Mosquitto MQTT Docker container for use with Home Assistant — Home Automation Guy
A guide for Node Red in docker and home assistant is here - Installing Node Red in Docker for Home Assistant
Container is definitely a harder install type to manage - that’s why the HASOS option is easier to manage. I feel your pain on the breaking changes. I’m not as able to be involved as I was a few years back due to job changes so have moved to more of a maintenance mode with my smart home, and get frustrated when things break. I try not to complain anymore though because I keep in mind I would rather use a solution that is actively managed and receiving updates from something that is no longer maintained. There’s really nothing else I’ve seen on the market that works better than Home Assistant, so I fix it and move on when something breaks. I also can understand why the developers are focusing on the two install types and no longer supporting supervised and core - No one likes to see their install type removed from support, but it is just too much to expect them to maintain all of these options and be able to fully support the product.