If you are referring to the first problem, it is too late for that now as I did a fresh reinstall. But thank you so much.
Now I am stuck with the other issue which it seems to be a recent issue. @Markymark posted this link above: https://github.com/home-assistant/supervised-installer/issues/217
From my understanding, the last version of HA breaks the network of the host OS. Any idea what version to install and how to actually install an older version of HA?
A PR has been merged to the installer which may address the network issue.
Hi,
I was getting this error and I applied your suggested fix.
However I am still getting this error 
`E: The repository ‘Index of linux/ubuntu/ bookworm Release’ does not have a Release file.
I am doing this on Rpi 4 (4gb ram)
sudo apt update && sudo apt upgrade -y
Hit:1 http://deb.debian.org/debian buster InRelease
Ign:2 https://download.docker.com/linux/debian bookworm InRelease
Err:3 https://download.docker.com/linux/debian bookworm Release
404 Not Found [IP: 18.67.111.89 443]
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Hit:5 http://deb.debian.org/debian buster-updates InRelease
Reading package lists... Done
E: The repository 'https://download.docker.com/linux/debian bookworm Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
my /etc/apt/sources.list
cat /etc/apt/sources.list
deb http://deb.debian.org/debian buster main
deb-src http://deb.debian.org/debian buster main
deb http://deb.debian.org/debian-security/ buster/updates main
deb-src http://deb.debian.org/debian-security/ buster/updates main
deb http://deb.debian.org/debian buster-updates main
deb-src http://deb.debian.org/debian buster-updates main
Did some more reading, could it be because I installed Debian 12? I just went to this page and got the latest, Tested images. I see a few comments suggesting version 12 is not supported.
@kanga_who I wonder if adding to your guide could help noobs like me not download the wrong version And then spending hours not understanding why it doesn’t work
adding to your guide could help noobs like me
This installation method is not meant for noobs!
This method is considered advanced and should only be used if one is an expert in managing a Linux operating system, Docker and networking.
This comes from ADR-0014
Fair enough, I am just happy I figured it out on my own, It’s working now 
This guide is not for a Pi, there is a seperate guide for that.
The name of the guide is “Installing Home Assistant Supervised on Debian 11”
No worries, agreed! I think that’s what’s go me relaising I was on the wrong path
Sorry I must have had both guides open, I was following the Pi guide and posted on the wrong one, sorry
This works! 
well done and thank you 
Super!!
Thank a lot!!
Works like a charm. Just installed Debian 11 + HASSIO Supervised on a Dell Laptop.
Thank you!
Is this still relevant - given that these instructions were posted in MAY 2020? (post #1)
It is. The OP keeps it always current (last edit as of today): 10 days ago.
hi @francisp , do you know how to disable portainer so that it won’t start during boot? I could remove it as well, find I sometimes find it useful, that’s why I would like to keep it disabled and just launch it when needed. I guess that HA won’t complain if portainer is not running during boot?
i followed this how-to exactly, just that my raspi is booting with PXE from NFS. Sadly the system losses connection as soon as the supervisor container is started. I’s supecting that the nework is being reset by the supervisor and thus i’m loosing the terminal and hassio is loosing its root fs… 
Ouch, yes, sorry. Indeed i followed this other guide, and i meant to comment there. Thanks for the super fast reply though!
Worked like a charm on installing Debian 11 on my Intel (Celeron) NUC through PXE.
hi, anyone else with an unsupported install due to connectivity_check? the link takes me here:
But after executing the command on the host and rebooting the problem still exists. Greetings and thank you
[Edit]
it seems that this is already being dealt with