Why *shouldn't* I use a container install

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:

  • all stopped containers
  • all networks not used by at least one container
  • all dangling images
  • all build cache

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 :grimacing: :rage:

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.

1 Like

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.

1 Like

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. :grinning_face_with_smiling_eyes:

1 Like