You didn’t get the memo? You’re not supposed to mess with HassOS. 
1 Like
lol - I’m not trying to mess with it, I’m trying to put a snapshot on it so I can restore my configuration 
(PS - nice to see you posting on the boards again 
)
1 Like
Well, see, HassOS is supposed to be this magical box…
I’m just messing with you. I have been laughing all morning at this announcement (I was out enjoying nature all day yesterday and missed the announcement). The way this whole thing has been handled is like watching open mic night at the local pub.
Communication is hard I guess.
2 Likes
But surely you are not suggesting (add hint of sarcasm/irony here) that the devs would make it difficult for anyone to use supervisor in anything other than a vanilla Pi with an SD ???
3 Likes
I’m finding a lot of ‘cart coming before the horse’ and this is just another example.
Them: We’re getting rid of this so from tomorrow you’ll have to follow the new official guide.
Us: OK, where’s the new official guide?
Them: We haven’t written it yet, it’ll maybe be here around xmas…
I’ll happily write migration guides and contribute all sorts of fun and easy-to-follow stuff for their new target audience, but none of it is working and there doesn’t seem to be any intention to introduce working things before deprecating the old working way. It’s worrying, although there is a slight reprieve as the decision has been suspended.
For now 
1 Like
Seeing that you are experimenting with a supported flavor of installation, can you try something easy for me?
You need to be able to open a console in the homeassistant container. I’ve done that using portainer. From there, ping a machine on your local network using its unqualified name. In my case, this fails:
ping io
However, it does work using the machine’s fully-qualified name (or IP address):
ping io.local
If you try the same thing in these containers, hassio_cli, hassio_dns and hassio_supervisor, it will work with unqualified names. It only fails in homeassistant and hassio_multicast.
In a nutshell, the homeassistant container is unable to resolve unqualified names using Home Assistant Supervised on Ubuntu. I’m curious to know if it works when it’s HassOS.
FWIW, if you’re interested, I discovered the difference between the containers that can and cannot resolve unqualified names and posted it here. I reported it as a bug but the issue was dismissed.
I will try next time I fire it up 
1 Like
So it seems the gang is all here now… 
So this is a pretty basic question i’m sure but I really don’t know the answer…
What exactly is Proxmox?
is it it’s own OS or does it run on top of another OS?
TBH, I haven’t even googled it yet. I’ve been too busy keeping up on the other thread.
If you don’t want to answer and just tell me to “google it noob” I’m ok with that too.
1 Like
It’s a hypervisor which is basically a minimal operating system purpose-built to manage virtual machines.
I believe Proxmox is based on Debian. In other words, there’s just enough Debian there to allow it to host and manage virtual machines.
It’s a hypervisor based on Debian.
Both. If you download the ISO it’s a customized Debian that just runs bare essentials to get Proxmox working (sound familiar?)
There is a way you can install it on top of your Debian install of choosing also. Shockingly enough, it’s a SUPPORTED option!
2 Likes
noob, - 
He’s been here 5 months less than you (but he is a lazy SoB, a bit like me really cos I had never heard of it )
1 Like
LOL. He’s referring to Proxmox noobery. I have been running Proxmox for nearly 12 years now.
Ah ! so YOU need to be writting the manual for ALL us proxmox noooooooobs !
Well … - … if they DO deprecate generic linux install !
Not bloody likely!
I refuse to use HassOS. 
I have a NUC running Alpine Linux running core on docker, and I have everything I need through Docker, have complete control over my entire system, and don’t have any of the issues that people continually post about with their setups. My stuff runs phenomenally stable. I have actually posted my setup before…I think it was about 3 years ago, and not much has changed on it. Still running pretty much the exact same setup, just updating HA when x.1/2/3… are released (and keeping my containers updated docker-compose pull && docker-compose up -d
I have my appliance dialed in just fine.
1 Like
Awwww … … … Not even if I say “pretty please with sugar on it” ?
Ah (word substituted as “Largest Island in Thailand” ) we’ll just see what ‘next week’ brings us
1 Like
I’m pretty much exactly the same except for a couple of details - I use Debian and I’m at least willing to give HA Supervised a try.
I’m pretty new on testing HA Supervised but it’s been running for a couple of weeks now including spanning an upgrade but I don’t see how people are having so many issues with it that it would cause so many “support/maintenance issues” beyond the normal issues for HA updates in general…
Besides I thought we were the support system for people who have issues. I’ve seen what the response is to someone who comes on here directly asking a dev for help. 
BAN HAMMER So it’s not like they are getting overloaded giving support for people asking for help in the forums.
You know me better than I thought! 
1 Like
Over the last 4 years, I have tried every available option for running HA. Over the last 3 years, I try out the supervised option in a VM about every 6 months to see what the fuss is about. It doesn’t appeal to me in the slightest.
That’s known as the “KarmHA Sutra”
2 Likes
I like to think of it as “thinking about what you are doing” rather than “flailing around just in the hope that you’ll eventually get where you wanted to be”
1 Like
I pretty much completely agree.
Every time I’ve tried it I never actually make the switch in my production system and just keep coming back to HA core in docker.