Stopping HA Autoupdate?

[kayasaman]

Hi guys,

I’m running a pretty substantial HA build on top of Arch Linux. Right now I’m fighting with the system as it keeps auto updating on me and I haven’t told it to do so?? It’s getting pretty annoying and frustrating because I have to keep rebuilding the docker instance from scratch which defeats the purpose, almost every day now? .

Basically eons ago I installed Hassio, so I have a systemd service called: hassio-supervisor

Now currently in docker I am using these containers:

docker container ls
CONTAINER ID   IMAGE                                                     COMMAND   CREATED             STATUS             PORTS                                       NAMES
bd46f17646ff   ghcr.io/hassio-addons/traccar/amd64:0.18.0                "/init"   3 minutes ago       Up 3 minutes                                                   addon_a0d7b954_traccar
ca85eb97a66c   ghcr.io/hassio-addons/bitwarden/amd64:0.19.1              "/init"   57 minutes ago      Up 57 minutes      0.0.0.0:7277->7277/tcp, :::7277->7277/tcp   addon_a0d7b954_bitwarden
550722c5243c   ghcr.io/hassio-addons/bookstack/amd64:1.6.1               "/init"   57 minutes ago      Up 57 minutes      0.0.0.0:2665->80/tcp, :::2665->80/tcp       addon_a0d7b954_bookstack
79b263e26b0a   ghcr.io/hassio-addons/grocy/amd64:0.19.0                  "/init"   57 minutes ago      Up 57 minutes      0.0.0.0:9192->80/tcp, :::9192->80/tcp       addon_a0d7b954_grocy
4dfa28a76927   homeassistant/amd64-addon-configurator:5.5.0              "/init"   57 minutes ago      Up 57 minutes                                                  addon_core_configurator
50b7833adf39   ghcr.io/hassio-addons/nut/amd64:0.11.1                    "/init"   About an hour ago   Up About an hour   0.0.0.0:3493->3493/tcp, :::3493->3493/tcp   addon_a0d7b954_nut
cd530d656434   ghcr.io/home-assistant/amd64-hassio-multicast:2022.02.0   "/init"   About an hour ago   Up About an hour                                               hassio_multicast
b20785dab48c   ghcr.io/home-assistant/amd64-hassio-audio:2022.07.0       "/init"   About an hour ago   Up About an hour                                               hassio_audio
edc1a7774d76   ghcr.io/home-assistant/amd64-hassio-dns:2022.04.1         "/init"   About an hour ago   Up About an hour                                               hassio_dns
ffbb492934ca   ghcr.io/home-assistant/amd64-hassio-cli:2022.11.0         "/init"   About an hour ago   Up About an hour                                               hassio_cli
11061a89f555   homeassistant/amd64-hassio-supervisor                     "/init"   3 days ago          Up 5 minutes                                                   hassio_supervisor
1fa5397e1c58   ghcr.io/home-assistant/amd64-hassio-observer:2021.10.0    "/init"   6 days ago          Up About an hour   0.0.0.0:4357->80/tcp, :::4357->80/tcp       hassio_observer

and these images are installed:

 docker ps --all
CONTAINER ID   IMAGE                                                     COMMAND   CREATED              STATUS                       PORTS                                       NAMES
e1a976e03a18   ghcr.io/hassio-addons/traccar/amd64:0.18.0                "/init"   About a minute ago   Up About a minute                                                        addon_a0d7b954_traccar
12b3f62ef011   homeassistant/qemux86-64-homeassistant:2022.11.1          "/init"   11 minutes ago       Exited (111) 7 minutes ago                                               priceless_haibt
ca85eb97a66c   ghcr.io/hassio-addons/bitwarden/amd64:0.19.1              "/init"   About an hour ago    Up About an hour             0.0.0.0:7277->7277/tcp, :::7277->7277/tcp   addon_a0d7b954_bitwarden
550722c5243c   ghcr.io/hassio-addons/bookstack/amd64:1.6.1               "/init"   About an hour ago    Up About an hour             0.0.0.0:2665->80/tcp, :::2665->80/tcp       addon_a0d7b954_bookstack
79b263e26b0a   ghcr.io/hassio-addons/grocy/amd64:0.19.0                  "/init"   About an hour ago    Up About an hour             0.0.0.0:9192->80/tcp, :::9192->80/tcp       addon_a0d7b954_grocy
4dfa28a76927   homeassistant/amd64-addon-configurator:5.5.0              "/init"   About an hour ago    Up About an hour                                                         addon_core_configurator
50b7833adf39   ghcr.io/hassio-addons/nut/amd64:0.11.1                    "/init"   About an hour ago    Up About an hour             0.0.0.0:3493->3493/tcp, :::3493->3493/tcp   addon_a0d7b954_nut
cd530d656434   ghcr.io/home-assistant/amd64-hassio-multicast:2022.02.0   "/init"   About an hour ago    Up About an hour                                                         hassio_multicast
b20785dab48c   ghcr.io/home-assistant/amd64-hassio-audio:2022.07.0       "/init"   About an hour ago    Up About an hour                                                         hassio_audio
edc1a7774d76   ghcr.io/home-assistant/amd64-hassio-dns:2022.04.1         "/init"   About an hour ago    Up About an hour                                                         hassio_dns
ffbb492934ca   ghcr.io/home-assistant/amd64-hassio-cli:2022.11.0         "/init"   About an hour ago    Up About an hour                                                         hassio_cli
d76fd736560d   homeassistant/qemux86-64-homeassistant:2022.11.1          "/init"   8 hours ago          Exited (111) 8 hours ago                                                 gallant_einstein
11061a89f555   homeassistant/amd64-hassio-supervisor                     "/init"   3 days ago           Up 13 minutes                                                            hassio_supervisor
bb11a7022f66   homeassistant/amd64-addon-letsencrypt:4.12.8              "/init"   6 days ago           Exited (0) 6 days ago                                                    addon_core_letsencrypt
1fa5397e1c58   ghcr.io/home-assistant/amd64-hassio-observer:2021.10.0    "/init"   6 days ago           Up About an hour             0.0.0.0:4357->80/tcp, :::4357->80/tcp       hassio_observer

I have just had to remove the docker 2023-03-06 container for homeassistant/qemux86-64-homeassistant

which I have no idea how got there…??

I elected to install version 2022-11-01 as I have been following the docker images:
https://hub.docker.com/r/homeassistant/qemux86-64-homeassistant/tags?page=9

It seems from 2023 onwards too many things break in my install so if possible I’d like to stick with the 2022-11 image until I can figure out a way to update the Supervised install as with 2023 images, my Addons section in settings disappears as well as all my addons including the all important File Editor.

Could someone fill me in on what’s going on and how to achieve what I want?

Having read around a little and particularly this thread: Where is the add-on store when running from docker? - #29 by NeilP

it looks like things have changed a little in the meantime but I couldn’t quite follow?

Basically all I am trying to figure out is how to keep the Supervised version of Hassio over the 2023 version of HA which gets installed and directly breaks my addons? Or if I could get the 2023 version to show the addons section that would be even better

Thanks for any advice

[tom_l]

Feature request: block supervisor auto-updates

This entire FR is about being able to stop supervisor from auto-updating. So, supervisor? But also none of the other stuff you listed auto-updates so I’m confused by your question. Or are you asking when it arrives in the UI? If so the answer is it doesn’t. There’s no UI toggle, its in the cli. ha supervisor options --auto-update=false Btw for anyone looking to do this, two important notes: If supervisor is out of date then all updates are blocked. Core, OS, addons, none of it can be update…

[kayasaman]

Hi, thanks for the response!

Sorry for the confusion… what I am really asking for is why it seems that HA auto updates the images automatically?

I haven’t told it to do so… perhaps I am misunderstanding something, I don’t know?

But really the problem for me is that I loose certain GUI elements like the Addons section:

What’s strange is that I have just deleted and removed the docker images and containers for HA then restarted the hassio-supervisor service then everything is working fine again.

I’m not sure why it seems like I have to do this on a daily basis otherwise I loose many things??

Also when container 2022 is installed why do I suddenly get a 2023 image?

docker container ls -a
CONTAINER ID   IMAGE                                                      COMMAND   CREATED          STATUS                  PORTS                                       NAMES
1dd9c75b168d   ghcr.io/home-assistant/qemux86-64-homeassistant:2023.3.6   "/init"   34 seconds ago   Up 33 seconds                                                       homeassistant
40346e232f27   ghcr.io/hassio-addons/traccar/amd64:0.18.0                 "/init"   2 minutes ago    Up 2 minutes                                                        addon_a0d7b954_traccar
e56a4e7fb75b   ghcr.io/hassio-addons/bitwarden/amd64:0.19.1               "/init"   10 minutes ago   Up 10 minutes           0.0.0.0:7277->7277/tcp, :::7277->7277/tcp   addon_a0d7b954_bitwarden
cf29e3492edd   ghcr.io/hassio-addons/bookstack/amd64:1.6.1                "/init"   10 minutes ago   Up 10 minutes           0.0.0.0:2665->80/tcp, :::2665->80/tcp       addon_a0d7b954_bookstack
48c8898e6345   ghcr.io/hassio-addons/grocy/amd64:0.19.0                   "/init"   10 minutes ago   Up 10 minutes           0.0.0.0:9192->80/tcp, :::9192->80/tcp       addon_a0d7b954_grocy
2f6901b4ca55   homeassistant/amd64-addon-configurator:5.5.0               "/init"   10 minutes ago   Up 10 minutes                                                       addon_core_configurator
1336f637c4a5   ghcr.io/hassio-addons/nut/amd64:0.11.1                     "/init"   13 minutes ago   Up 13 minutes           0.0.0.0:3493->3493/tcp, :::3493->3493/tcp   addon_a0d7b954_nut
6481e79c684e   ghcr.io/home-assistant/amd64-hassio-multicast:2022.02.0    "/init"   13 minutes ago   Up 13 minutes                                                       hassio_multicast
893c314e3d7f   ghcr.io/home-assistant/amd64-hassio-audio:2022.07.0        "/init"   13 minutes ago   Up 13 minutes                                                       hassio_audio
487916e963d3   ghcr.io/home-assistant/amd64-hassio-dns:2022.04.1          "/init"   13 minutes ago   Up 13 minutes                                                       hassio_dns
928295499c1d   ghcr.io/home-assistant/amd64-hassio-cli:2022.11.0          "/init"   13 minutes ago   Up 13 minutes                                                       hassio_cli
11061a89f555   homeassistant/amd64-hassio-supervisor                      "/init"   3 days ago       Up 2 minutes                                                        hassio_supervisor
bb11a7022f66   homeassistant/amd64-addon-letsencrypt:4.12.8               "/init"   6 days ago       Exited (0) 6 days ago                                               addon_core_letsencrypt
1fa5397e1c58   ghcr.io/home-assistant/amd64-hassio-observer:2021.10.0     "/init"   6 days ago       Up 13 minutes           0.0.0.0:4357->80/tcp, :::4357->80/tcp       hassio_observer

I’m probably not explaining very well at all I really apologize for this.

Basically why do I keep loosing my Addons section after a day or so?

This is really what I am trying to figure out… if that makes sense??

[kayasaman]

@tom_l I think what’s confusing me the most here is when I issue a pull statement in docker for version 2022:

docker pull homeassistant/qemux86-64-homeassistant:2022.11.1

Somehow this guy keeps creeping in:

ghcr.io/home-assistant/qemux86-64-homeassistant:2023.3.6

That’s probably why I am thinking that there is some kind of auto update mechanism. Because to me, by initiating the pull statement for the previous version; it should tell the system to explicitly use that?

At the moment things are looking like they are working but after a reboot I am not quite sure what will happen to be honest.

Previously I had weird “recorder” issues in the logs too stating ‘invalid config’ ??? No idea how those came about either…

Hopefully now I won’t loose things as they are now, which kind of prompted me to ask in the first place as I’m left completely confused as you can probably tell…

I’ll see how things get on from here

[tom_l]

@kayasaman

Sorry for the confusion… what I am really asking for is why it seems that HA auto updates the images automatically?

The only automatic update HA does is for the supervisor container. For which I linked you to a post showing how to disable that.

You appear to be running quite a non-standard installation. If you want a docker install just do a Container Install and manage your own containerised applications rather than using HA add-ons.

Take note of what is and is not included in a container install: https://www.home-assistant.io/installation/#compare-installation-methods

[kayasaman]

Thanks! Yep it is quite non standard

I know you can manage the addons separately but to be honest, I’m not that familiar with Docker, therefor I guess it’s nice to have a safety net in the GUI web interface if things go pop, plus it’s a lot easier to update things…

Though having said that I’m actually doing 2x FreeBSD upgrades as I type this for two of my backend servers, one of which I need to compile the whole environment from scratch because I was running a now obsoleted version of the -CURRENT branch. …looks like it’s gona be another all nighter for me

I’ll definitely read through the links and see if I can gain some better understanding to things.

[nickrout]

You are using a very non standard supervised install. There are now only 4 official installation methods, and one of them is supervised. The requirements for supervised are narrow and set out in the docs. Arch unfortunately is not supported, only Debian 11.

The only other official way to get the supervisor and therefore addons is to go with HA OS.

I do not know what is auto updating your system. You don’t have a program called watchtower installed do you? It automatically updates docker containers.

[kayasaman]

Thanks Nick…

I’ll read up on HA OS, HomeAssistant development seems to be moving faster then I can keep up.

I don’t have anything like “Watchtower”; it’s weird…

Probably no point in posting this but here’s the service unit that I have:

# cat /etc/systemd/system/hassio-supervisor.service
[Unit]
Description=Hass.io supervisor
Requires=docker.service
After=docker.service dbus.socket

[Service]
Type=simple
Restart=always
RestartSec=5s
ExecStartPre=-/usr/bin/docker stop hassio_supervisor
ExecStart=/usr/sbin/hassio-supervisor
ExecStop=-/usr/bin/docker stop hassio_supervisor

[Install]
WantedBy=multi-user.target

Maybe there’s something in the SuperVisor binary in /usr/bin??

I would guess it to be highly unlikely…

To be honest I don’t mind the update, as long as I get the Supervised Install back. This seems to be causing the problems because after updates somehow the system changes and many errors get reported back. I’m not sure why so it’s probably me worth attempting to track that down and perhaps creating another thread? more specific to the issue/(s)

It’s just strange and right now I feel like a passenger not in control

[nickrout]

To be clear, the supervisor is designed to update itself. Core isn’t.

Anything in crontab?

[tom_l]

@kayasaman

I feel like a passenger not in control

Well you are driving the equivalent of a cart with 3 and a half wheels pulled by a herd of cats.

Try a supported installation.

[kayasaman]

Nothing in crontab… unfortunately

[kayasaman]

I wanted to use Arch because I am most familiar with it and need other services on the system alongside HA… mainly stuff like SNMP, NTP and I also have a Xeoma installation on the same box.

Due to lack of space I’m even running iscsi from my main storage pool for the /var/lib/docker mount point. It might have been contributed to using the older style storage and not overlay2… switching from JFS to EXT4 file system changed that

The biggest problem for me really is that HA connects to a much larger environment, even using Postgresql as DB backend.

I’m sure Debian can handle everything… I have not used in years not since the days of version 8?? Sarge named branch…

This is the actual physical install for my HA and where it fits in my environment:

I did create a post about somewhere a long time ago here on the forum about integrating HA together with the industrial grade CarloGavazzi VMU-C MODBUS based energy logger.

HA really does work well and is so easy to integrate as long the other side has an open API…

But will need to see if I it’s actually possible for me to migrate over. I initially started with the HASSIO appliance image but found that way too light for what I needed which is why I went my own route

[nickrout]

Consider proxmox. Run your arch in a vm. Run haos in a vm. Or run debian + supervised in a vm. Have a play.

[kayasaman]

Hi everyone… thanks for all the help and apologies for being a little distant lately. I just had fiber optic WAN cabling installed and have been trying to use both ISP’s which is proving difficult on my router (self built)
It really is just a case of routing but not sure how to approach it as on the base OS things get complicated very quickly… how I yearn for Cisco simplicity at this moment

I think in all this, what I have been doing wrong is starting docker. Having been quite distracted I didn’t realize that the hassio-supervisor service does that anyway. I even wrote it above when I posted the service unit which is really embarrassing!!

Basically from my psuedo startup script, the only thing I need to do is run the sysctl command for the suprevisor service and forget about the other stuff:

#!/bin/sh
iscsiadm --mode discovery --portal x.x.x.x --type sendtargets
iscsiadm -m node --targetname=iqn.domain:target4 --login
#mount /dev/sdc1 /var/lib/docker
sleep 30
fsck -p /dev/sdc1
sleep 60
mount /dev/sdc1 /var/lib/docker
#systemctl restart systemd-journal-gatewayd
#systemctl start docker
#systemctl start hassio-supervisor

Having been forced to do a bunch of reboots everything seems to be ok now. Obviously I’ll keep monitoring but for now I apologize for the noise!!

I really hate it when panic sets in because my comms room (ie would be bedroom) had no air con for a while due to HA being off and the temperature gets high enough to strip paint off the walls.
Basically for me HA is a critical system
In fact everything is controlled by HA and actually I have no physical overrides for many things because they straight into HA either over the network or through the GCE IPX system sitting in my electrical cabinet.

Anyway, now on to trying to fix my second WAN connection and seeing if I can get the BSD equivalent of a “Route Map” up and running grrrr

Again thanks to everyone for all your help!!! It is really appreciated