I appreciate the effort and thank you for the pointers. The goal was not going off topic but I was requested some reasons
Try my fixed script for i386 netbook:
Shortly. It is to fire up Supervised installation that will have common updates on Debian 11 i386 netinst distro even without any GUI via SSH.
sudo apt install software-properties-common python3.9 python3.9-dev python3.9-venv python3-pip libffi-dev libssl-dev
sudo apt autoremove -y
export PATH=$PATH:/usr/sbin
sudo apt install apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat bash
systemctl disable ModemManager
systemctl stop ModemManager
sudo apt install -y docker.io
sudo apt install wget unzip udisks2
wget https://github.com/xvrfr/homeassistant/raw/main/os-agent_1.2.2_linux_i386.deb
sudo dpkg -i os-agent_1.2.2_linux_i386.deb
wget https://github.com/xvrfr/homeassistant/raw/main/supervised-installer.fixed.sh
chmod 777 supervised-installer.fixed.sh
sudo ./supervised-installer.fixed.sh
All dependencies are original non-modified except installer script. Modification of Kanga-whoâs script had to be implemented because services filesâ and cli download links now give 404 error.
On the other hand, if you have gui then try homeassistant-supervised.deb which should ask you for machine-arch. Choose qemux86.
I donât know the way to pass machine parameter to deb via dpkg installation not to get its post-installatuon scripts error. Thatâs why I used fixed installation script.
(read with google translate or ask here for more help)
Run this on the host
echo "kernel.dmesg_restrict=0" >> /etc/sysctl.conf
sysctl -p
4 Likes
What for? It is the same even before appending⌠Or that post wasnât for me?)
Hi All,
Is there a way to create an entire image of my SSD that contains Debian & Home Assistant? For my Windows machines I use the excellent Macrium Reflect, I have created a USB rescue stick that allows me to boot from this and either create an image to an external HDD or restore an image from an external HDD. Iâd like to make make regular backups of my HA machine as I do with my Windows machines, in case of a failure it would be easier to restore an image rather than have to completely reinstall Debian from scratch then Home Assistant and restore a backup that I make and store on my NAS.
Just curious if anyone else does this?
There is no real need to do this when installing Debian and restoring a backup of HA can be done in about 20mins.
Keep regular backups of HA and in the unlikely event your SSD fails, reinstall Debian and restore HA.
I hear you,
I was just trying to make it a little easier, I have images of all my other machines so I figured why not do the same with my HA machine
For the time it takes your Pi and HA offline, image the disk and so on, it seems a little pointless when itâs so quick to reinstall and the chances of needing to do it when using an SSD is very low.
If it saves time having to configure/set up Debian then why not image it? Network settings, users, permissions, changed repositories, etc. Now, if you load up a Proxmox VE box, the built in backups/snapshots of VMs and containers are a thing of beauty and virtually eliminate the need for images.
1 Like
If you think the time spent doing this regularly enough (weekly/monthly) to have a recent working back up is time better spent than 20-30mins every ~2 years if an SSD fails, then go nuts.
In the time span an SSD should and will last, you will most likely move to another machine making the imaging redundant.
Still having this issue:
Error response from daemon: Get âhttps://registry-1.docker.io/v2/â: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:60704->[::1]:53: read: connection refused
dpkg: error processing package homeassistant-supervised (âinstall):
installed homeassistant-supervised package post-installation script subprocess returned error exit status 1
Already disabled IPv6, but still no goâŚ
Anyone having any suggestions??
Maybe @RVitalâs workaround helps?
Add to /etc/hosts:
140.82.121.34 ghcr.io
185.199.108.154 pkg-containers.githubusercontent.com
Tried it with
140.82.121.34 ghcr.io
But seems to be an issue with dns in relation with IPv6
tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:60704->[::1]:53:
And now that i look at itâŚmaybe add
registry-1.docker.io ??
At lastâŚ
34.203.135.183 registry-1.docker.io
140.82.121.34 ghcr.io
Stared at it for a couple of days, searched for a solution a couple of days, but answer was right in front of me the whole time 
Thanks for making me see @Tamsy !!
PS: Not sure if this is (still) required, but it canât hurt to add it 
185.199.108.154 pkg-containers.githubusercontent.com
Anoyher and probably more viable solution than the above workaround (ip addresses can change at any time) can be found here.
Hi guys,
How can I get docker-compose to work and avoid the âYou are running an unsupported installationâ ?
Had the system running fine, then tried to do `sudo apt install docker-composeâ
Now I have the âYou are running an unsupported installationâ and afaik I will not be able to do updates when this message are active?
you canât avoid unsupported if you install compose. But that wonât prevent you getting updates as normal. Even if you get the unhealthy message as well there is a cli command to tell HA to ignore it and you will get updates as normal.
Thanks @DavidFW1960 
After I did the sudo apt install docker-compose, my NetworkManager got screwed up. Are there any other way to get docker-compose installed to avoid messing with NetworkManager?
btw; do you also have the CLI command you did mention (for my own records) ?
Look at Section 4 paragraph 3 within the OP.
Somewhere around Section 2.1 the guide needs to be updated.
Debian is now shipped with ifupdown. This will interfere with network manager.
If the following message is shown when installing network manager:
The following network interfaces were found in /etc/network/interfaces
which means they are currently configured by ifupdown:
- eno1
If you want to manage those interfaces with NetworkManager instead
remove their configuration from /etc/network/interfaces.
Then the file: /etc/network/interfaces needs to be edited. In my case the lines with eno1 (my ethernet) needs to be commented out, before proceeding. If this is NOT done, the machine will crash and nothing will work.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eno1 <-- This should be commented out
iface eno1 inet dhcp <-- This should be commented out
Remember to reboot before proceeding.
1 Like