No, HassOS is the host on a hassio IMAGE install…That would be outside of the docker environment, and it requires special parameters to SSH into it. I am 100% referring to management OUTSIDE the docker container.
If you are talking about running hassio on a normal Linux OS, then you have access to everything you need because YOU control the underlying OS. So I will reiterate that HassOS is limited in operation, and you simply cannot use the Linux tools you are familiar with on it. Zero control.
By default, when someone says they are running Hassio, it is assumed HassOS, because of the way the Home Assistant markets it. If you are running Hassio under docker, you have to specify that. They are different ways of running hassio.
You can however run all your Linux stuff AND run HassIO… Ubuntu / Debian --> Docker --> HassIO You would run them directly on the Lunix underneath? HassIO. This is where you can have the win-win situation of a full Linux base OS plus HassIO (with it’s handy add-ons)
EDIT: just re-read flamingm0e’s post which says this anyway. It may however be dangerous to assume that people are running their HassIO install with HassOS.
By default, when someone says they are running Hassio, it is assumed HassOS, because of the way the Home Assistant markets it.
I’m not sure how valid that is anymore. I’d say maybe 80% use HassOS, with the market share of HassIO on normal linux having increased lately it seems.
The problem stems from the naming convention they have chosen. HassIO refers to the “ecosystem” but there is no distinction on the front page. From what I have seen, so many people don’t understand the difference, and typically say “I installed HassIO” simply because that’s how it’s marketed. The default installation method if you are using the getting started guide is to install the hassos image.