Supervisor in privileged mode

Configuration
1

I installed hassio so long ago that it doesn’t run the hassio supervisor in privileged mode.
Some anserws in this forum just says “run supervisor in privileged mode”.
What do I do to make that happen? I assume there’s a file somewhere in the host system (Debian 9 in my case) that I can edit. Which file is it and what do I have to do?
I’d rather not wipe everything and reinstall from scratch.

2

I found a way. I think.
The host system folder
/var/lib/docker/containers/728b1382b7bb26a4514be60d52140c2669e25317e3bb7f668e9070047002d01c
contains the hassio-supervisor container.
There’s a file in there: hostconfig.json It contains a lot of configuration options for this container.
So I did the following:

  1. I logged into the HOST system with ssh.

  2. I stopped docker with
    systemctl stop docker

  3. I changed “Privileged”:false to “Privileged”:true

  4. I rebooted the host system.

So far it seems to work, and the error message saying the supervisor is non-privileged is gone!

4 Likes
3

How do you ssh hassio? I get the following:

# systemctl stop docker
Connection to hassio closed by remote host.
Connection to hassio closed.
4

I ssh into the Debian host system, not the hassio docker.

5

I understand that. The point is what I find is this: https://developers.home-assistant.io/docs/en/hassio_debugging.html which leads to getting into the host system through the docker still. How have you managed SSH directly to the host system?

6

My installation is Hassio docker on an Intel NUC with Debian 9. Most of the installations on it have been done via ssh from another computer.
The host system is available in the network via the default ssh port, so i just use ‘ssh ha’, where ha is defined in my local hosts file.
You have to have a username and password on the host, of course.
(I’m not a linux expert, so I hope this is of some help.)

7

Ok, there we have it… I am on HassOS and I think that there is where I am stuck :frowning:
Even when I use the console (no ssh) if I shutdown the docker the whole system halts.
I think I’ll go for reinstalling the HassOS although it is very frustrating not getting down to this very “basic” thing to test. Thanks for you help.

8

Tx that helped for me as well!

9

Thanks @helgemor, This solved my problem!

1 Like
10

Does this stick after a reboot? I did this and was happy to see it works and the next update it’s saying it’s unsupervised again.

11

I have upgraded to Debian 10 this spring, and I haven’t seen that problem since. But i believe I had some reboots while on debian 9 as well, with out any problems. But, not sure.