You guys rock - And Hass.io / Docker best practices question

FIrst of all I want to thank the community. If you have written something about Hass.io configuration, its use with Docker, or Ubuntu, or so many other issues THANKS!.

As Windows quasi-technical guy I was able to get a brand new NUC, running Hass.io in a Docker container on Ubuntu server 16.04. I still remember trying to get HA running on my Pi the first time.

My goal for this project was to migrate away from Pi with Hass.io to a platform that has all the benefits of Hass.io but with the ability to incorporate some of my own python/other stuff. This seemed like the best of both worlds.

So if anyone has any wisdom/suggestions as to how to work with this setup going forward and avoid some pitfalls I would appreciate it.

I was initially worried about using the Hass.io Samba component as I thought I was sharing the container’s config when I wanted to be editing the config on the NUC that gets put into the container (for persistence reasons). My preliminary guess is the samba-addon container that gets created does this automatically.

I had my pynx584 server running on another old PC I wanted to migrate away and I am looking to implement CallerID but couldn’t get the modem visible in Hass.io on the Pi.

Its too often the people who help (You!) aren’t appreciated.

I’ll stop wasting bandwidth now.
Mike