[Feedback][Issue] CasaOS installer installs conflicting home-assistant-snap, breaks existing Docker HA

[MikkeMo]

Hi CasaOS team,

Today I installed CasaOS using the official command:

curl -fsSL https://get.casaos.io | sudo bash

Shortly after, my existing Home Assistant Docker container (ghcr.io/home-assistant/home-assistant) stopped working — opening the web UI showed the "Welcome! Create my smart home" onboarding screen as if all my data was gone.

After digging into it, I found that the CasaOS install had also installed "home-assistant-snap" as a snap package. The snap had bound to port 8123 first, blocking my real Docker container from binding. My data was completely fine — the snap was just intercepting all the traffic.

Evidence from my system:

• ss -tlnp showed python3.13 (snap) listening on 8123
• Docker container log: "Failed to create HTTP server at port 8123: [errno 98] address in use"
• My HA Docker container uses python3.14, so it was clearly a different process
• HA mobile app discovered two instances ("Home" and "Home-2") at the same IP
• Everything worked perfectly until the CasaOS install today

Fix:
sudo snap remove home-assistant-snap
docker restart homeassistant

Suggestions:

1. The installer should detect existing Home Assistant Docker containers and skip installing the snap
2. At minimum, warn the user before installing services that bind to common ports already in use
3. Consider not installing home-assistant-snap by default at all — most users with HA already have it set up the way they want

Otherwise, loving CasaOS so far. Thanks!