Supervisor update

DavidFW1960 · August 24, 2021, 9:46pm

No idea where to adjust the environment variables as we don’t use a docker run command anywhere or a script as the supervisor is a service. Where is the file to adjust those variables found? Is the best approach just to run the installation script again?

nickrout · August 24, 2021, 9:50pm

first of all find out if they are there already.

docker inspect hassio_supervisor|grep Env -A10

should catch your env variables.

DavidFW1960 · August 24, 2021, 11:13pm

                "SUPERVISOR_SHARE=/usr/share/hassio",
                "SUPERVISOR_NAME=hassio_supervisor",
                "SUPERVISOR_MACHINE=intel-nuc",

So just the machine name then. I’m thinking I just run the install script again…

DavidFW1960 · August 24, 2021, 11:49pm

no change.
So the script is writing to /etc/hassio.json looks like this:

{
    "supervisor": "homeassistant/amd64-hassio-supervisor",
    "machine": "generic-x86-64",
    "data": "/usr/share/hassio"
}

So the reinstall fixed that file.
The script is in /usr/sbin/hassio-supervisor

Maybe I can restart Supervisor? Nope!
Tried downgrading to 2021.8.7 but that’s not making it change the image it’s pulling either.

iscraigh · August 25, 2021, 1:04am

My file looks the same. I am a bit confused should we be changing the name to

“supervisor”: “hassio-supervisor”

Thanks

francisp · August 25, 2021, 2:51am

Yes, after apt install libglib2.0-bin I saw the osagent was installed correct.

greiss.lars · August 25, 2021, 7:17pm

If I remember correctly you are using home assistant supervised.

The service is located here:

/etc/systemd/system/hassio-supervisor.service

which is calling following script:

/usr/sbin/hassio-supervisor

where you will find the docker run command with the environment variables

EDIT: On my supervised installation they were already present

DavidFW1960 · August 25, 2021, 9:33pm

They were on mine as well but the machine type is wrong as I posted even though after reinstalling the json file has the correct machine in there. I did notice there is a new beta supervisor now and I’ll update to that soon. Perhaps it needs that supervisor to fix it.

greiss.lars · August 25, 2021, 10:10pm

I see. Well on my installation everything is configured as expected. I did nothing special…just the update

DavidFW1960 · August 25, 2021, 11:04pm

yes but I’m on an intel-nuc install which is now being replaced by generic.

            "Env": [
                "SUPERVISOR_SHARE=/usr/share/hassio",
                "SUPERVISOR_NAME=hassio_supervisor",
                "SUPERVISOR_MACHINE=intel-nuc",
                "PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "LANG=C.UTF-8",
                "S6_BEHAVIOUR_IF_STAGE2_FAILS=2",
                "S6_CMD_WAIT_FOR_SERVICES=1",
                "S6_SERVICES_GRACETIME=10000",
                "SUPERVISOR_API=http://localhost"
            ],

Everything is right but I can’t set a different machine type as I already posted.

the json file hassio.json:

{
    "supervisor": "homeassistant/amd64-hassio-supervisor",
    "machine": "generic-x86-64",
    "data": "/usr/share/hassio"
}

So it’s set for that just not getting into the script even after I reran the installer (Your installation machine hasn’t changed but mine has)

EDIT: Updated to the beta supervisor 2021.08.0 and loaded beta 2021.9.0b0 and it’s pulled generic! Now:

 "Env": [
                "SUPERVISOR_SHARE=/usr/share/hassio",
                "SUPERVISOR_NAME=hassio_supervisor",
                "SUPERVISOR_MACHINE=generic-x86-64",
                "PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "LANG=C.UTF-8",
                "S6_BEHAVIOUR_IF_STAGE2_FAILS=2",
                "S6_CMD_WAIT_FOR_SERVICES=1",
                "S6_SERVICES_GRACETIME=10000",
                "SUPERVISOR_API=http://localhost"
            ],

So looks like it needed the new supervisor to ‘take’ the machine change

pocket · August 26, 2021, 2:26am

I had a missing dependency; I needed to install the udisks2 package before the .deb file.

francisp · August 26, 2021, 2:47am

Me too. And after libglib2.0-bin

palito · August 26, 2021, 5:38am

I have opened an issue for that already. I had it missing too. Thanks to this thread I was able to solve it.

Btw what is the outcome of this? Future use? Or I can see something already now?

francisp · August 26, 2021, 5:43am

Well, I upgraded first to bullseye, and then installed osagent. So it is not standard on Debian 11 too.

nickrout · August 26, 2021, 6:14am

Do you have a hint for a simple way to update to bullseye?

francisp · August 26, 2021, 6:17am

In a console :

su
sed -i 's/buster/bullseye/' /etc/apt/sources.list
sed -i 's/buster/bullseye/' /etc/apt/sources.list.d/*.list
sed -i 's|bullseye/updates|bullseye-security|' /etc/apt/sources.list
sed -i 's/bullseye/buster/' /etc/apt/sources.list.d/*mosquitto*.list
apt update
apt upgrade
apt full-upgrade
apt autopurge

nickrout · August 26, 2021, 6:31am

That seems far too simple when you look at the official docs. Chapter 4. Upgrades from Debian 10 (buster)

Thanks.

palito · August 26, 2021, 6:36am

I have followed this and upgraded to Bullseye without issues.

DavidFW1960 · August 26, 2021, 7:18am

I think the official docs were even simpler actually… one line to replace buster with bullseye in all source lists and then the standard update and Disto-upgrade

nickrout · August 26, 2021, 7:56am

Its all the warnings and seeming gotchas that worry me.

Still I am on the final leg of @francisp 's instructions and will hold my breath and reboot shortly.