Are you sure you aren’t running the HA container as a container install in Synology? That makes more sense.
5 Likes
The same answer as I have given here applies to this one: Feedback requested: Deprecating Core, Supervised, i386 & armhf - #12 by frenck
1 Like
Sounds like a good move to me.
32bit support has been deprecated on many Open Source projects as there’s no real reason to still support it in 2025.
For normal users there should be no reason to still run Core or Supervised, for developers they can still run it, just without support from HA.
My guess is that some users run ‘unsupported’ versions when they followed a guide they found online, without really knowing what they are doing. And these users might give you more support requests as well. For those the HA OS installation is the easiest to use anyway.
6 Likes
I’ve followed a similar guide like 3-4 years ago How To Install Home Assistant Supervisor on Your Synology NAS – Marius Hosting
And thats the current result
But i see that Marius has posted an installation guide for a non-supervised (container only) version (at least thats what i assume) How to Install Home Assistant on Your Synology NAS – Marius Hosting
1 Like
Are you sure you are running Supervised on Synology? That hasn’t really been supported, so the proposed change wouldn’t affect your install, as it is already not supported.
That doesn’t say it won’t work, just that you won’t get support if you have issues.
Docker on Synology or HA OS through VMM on Synology will still work.
1 Like
That has never been supported (see our currently official documentation for supported installation methods and instructions).
This means, in this case, you are already running an unsupported/community-supported installation. Nothing will change, you will remain unsupported as you are already.
…/Frenck
5 Likes
Understood – it seems i just like living a dangerous life! 
3 Likes
naturally support for ancient platforms has to be withdrawn at some point, kinda surprising i386 has been supported this long.
same with core and supervised - too much that can go wrong/compatibility issues/things to screw up when it’s not part of the entire package with underlying OS. so no need for official support and a massive headache with it.
what I would love to see though, is official support/build as LXC container, effectively HAOS without kernel, with support for addons etc. main benefit being much better resource utilisation on the hypervisor.
4 Likes
Well I’m running haos in proxmox so it doesn’t bother me
1 Like
Get rid of those.
Why?
It’s easier to recommend something now.
Those people who know python and docker, know that they still can run it this way.
They will also understand that nothing is taken away.
Those who think something is taken away do not understand Python/Docker and should not use these installation methods.
Less options is better since it makes it clear to everyone what to use.
7 Likes
Time is money, so if you can do better investing your time for example more focus on the product itself, I’ll see; get rid of it!
3 Likes
I’m running Home Assistant in a Docker container using the image from: homeassistant - LinuxServer.io
The version in System Information shows core-2025.3.2
I run this alongside ESPHome, Mosquitto MQTT and some other unrelated containers on a single low-end x86-64 mini PC.
Having to dedicate a piece of hardware to an appliance style installation for a single app seems like a giant step backward to me. I hope I’m reading this wrong, but it seems like that would be the case if Core is deprecated.
Thanks! But that one isn’t supported by the Home Assistant project. Please see our documentation for the (current) officially supported installation methods and instructions.
In your case, you are already running an unsupported/community-supported installation method. Nothing will change for you. You’ll remain unsupported moving forward.
…/Frenck
4 Likes
Why are you running the LinuxServer version and not the official Docker Container? Does it offer anything the official one doesn’t?
If you want to use a different provider for your Container, they should support you and not HA itself. This is already the case, so nothing changes there.
3 Likes
The other day I was actually hoping for Supervised to become truely OSI-agnostic, more specifically fully Podman native… 
As for Core, I totally get that.
My concern was seeing Core listed in the system information. If the container I’m running is based on Core and Core goes away, it would have an impact, wouldn’t it?
It is quite possible, but again, your installation method is already not supported by the Home Assistant project. If you have questions about your installation, you should ask the LinuxServer project, not us.
We don’t maintain, build, or design those containers; nor do I have clue on what is in it. In the end, it doesn’t really matter, it remains unsupported. Just like it is today.
…/Frenck
2 Likes
When it comes to i386 and armhf, given that there are many Linux distros not even packaging for those architectures anymore, added to the fact that there’s a very small user base, I’m not opposed to the deprecation, it seems fairly logical.
As for Core and Supervised, I would very much like to know what changed since the last time this subject was brought up ([On hold] Deprecating Home Assistant Supervised on generic Linux - Home Assistant), with the rather lengthy discussion that followed which culminated in maintaining the four official install methods.
Also, I do hope I’m experiencing some sort of missing in translation error, because “Will take that feedback into consideration with the teams when we decide to move forward with this 
” reads to me that this is not a question of “Should we do this?”, but rather an “We’re going to do this, we’re just making it seem like it’s more transparent to avoid the amount of backlash we had last time we tried to do it”…
1 Like
I’m pretty self-reliant with my installation. My concern is if the upstream project goes away. If it’s just “not officially supported,” but still available, I have no problems with that.
Just do it bro, the stats dont lie, whatever makes it easier for the team to spend more time on the new cool stuff 
3 Likes