Ooh, I like yours better! Mine dates back from when I was trying to get my head around docker and shows. It’s more of a sledgehammer. It does:
cd # <to the HA compose file location>
docker compose stop
docker compose rm -f -v
docker compose pull
docker compose up --build -d
To yours, I’d just add the -f option to the last two commands. I’m going to say yes, anyway.
you could also just prune everything with:
docker system prune --volumes -f
which will remove:
I really dislike the idea of doing automatic updates to anything related to HA. So using watchtower etc is a no-go for me. The idea of waking up to leave for work (etc) and finding my home automation system is dead from a failed update is 
If you don’t want to auto update but still want the same ease of updates as HA provides then use Portainer. It’s literally 4 clicks and you’re done.
And since I have other HA Container installs I can update those first which pulls the new image during the update which is the longest part of the update process. Then when I do the update on my production install since the new image is already pulled it literally take no longer to update than just restarting HA.
I’ll be even more specific: docker run --privileged.
You might not need it, but there are definitely cases where this is needed. In fact, the official docs include this.
Your case is not everybody’s case and you don’t seem interested in other views and to just be nitpicking now, so this will be my last comment to you. My post was to advise the OP.
You shouldn’t not use a container install.
Why not? Over 50,000 installations (~17%) are reported using it this way.
edit: My bad - just read your post properly - sorry about that. I need a coffee.
We are talking about same thing. Why do you need this?
Stating a fact (this other thing is possible) is not nitpicking. You changing your reply to be more and more detailed to be correct. That may be better example
Anyway my point:
-docker is good
-Root or privileged not needed but you correct, skill level makes difference and likely needed on synology
-All install methods are great. Choose what’s easiest for your use. I also use HAOS on small installs
Yeah I had to read it twice myself.
that dastardly double-negative threw me for loop. 
Interesting topic. Old - but still valid point - some things might have changed?
I’ll swtich from OpenHAB to Home Assistant and I’d like to know:
How would you decide today?
Why you deceided this and why not the others?
Thaks for some more input.
I used to run HAOS (really like the supervised with addons) on a hyper-v virtual machine.
Ran into issues with USB support, so a year later I migrated to debian supervised.
That didn’t last long as I found out supervised restricted me and doesn’t allow any tampering, so i started HAOS as virtual machine on VMWare. Ran that for 3 years.
When I moved to another house a couple of months ago, i decided use use an old laptop (dell 5480, have plenty of them at the office as being ‘obsolete’, too old) and run HAOS dedicated. (with plenty of hardware as spares)
I’ve never got the hang of mcvlan / mdns. Could you share your docker compose that makes mdns work?
We’re in the big hardware change for windows 11 so here I am. I’ve been using supervised on a windows 10 VM machine with virtual box. I have to switch machines. Would it really be worth while to learn docker? I have no experience at all with using containers.
I run zwavejs and node red mostly.
just install vbox, and move the machine?
I do recommend vmware though; it is free for personal use, a bit steeper learning curve, but way more stable (and yes, you can migrate the vbox machine, but it is easier to take a backup and start from there)
Absolutely docker container, but this is because everything I host is docker container based.
Docker containers are really easy to set up (once one understands how docker works), and to backup. And to recover - which is the importnat part 
I recently did an exercise of Disaster Recovery when I switched the M2 disk of my server. I started from scratch (download the Debian ISO, …) and it took me about 1 hour without any documentation (including recovering from a remote backup - I had a local one but i wanted to go the hard way). This machine has everything - I just have a redundant Pihole installation somewhere else to cover exactly this case.