I am considering to use Proxmox VE on a Raspi5 with 256GB NVMe SSD. One LXC will hold a Pi-hole VM.
What would be the way to set up HAOS in another container? Are there preconfigured container images somewhere?
The steps I imagined up to now are
Sorry if this idea seems stupid - may be I am 
Found the answers while digging deeper into several videos and tutorials.
The list above continues as
So I hope, as my SSD will arrive tomorrow only. Fingers crossed…
Just in case you still haven’t gone through with it, this would be the easiest way to install HAOS Proxmox Helper Scripts | Proxmox Scripts For Home Automation
Thanks! I in fact had found these scripts but was not sure if these would work on the Raspi5 as well or have been written for x86 architectures only.
Hmm, not sure, but Proxmox is Proxmox - it should work.
Worst case scenario if it fails, just scrap the LXC.
There is a fork porting the helper scripts to arm64, so I might have been right. For the time being there is the HA Core only Github fork for Proxmox Helper Scripts
FYI: the ARM64 Proxmox port is running nicely with two LWCs (Pi-Hole and HA Core) with a system load of below 10%. You will have to use the ported helper scripts posted some steps above. I had to fiddle a bit with the network settings, but that may have been due to my ignorance at the first moves.
I rather would like to have the Supervised HA for the add-ons. Perhaps I will try that at another day 
Stuck again.
I tried to install the Supervised Home Assistant as advised on the HA web site and in fact succeeded, but the Home Assistant docker container has no access to the physical network.
ip address results in
~# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0@if30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:24:11:0d:f3:74 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.178.204/24 brd 192.168.178.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2002:95ac:a8ee:0:be24:11ff:fe0d:f374/64 scope global dynamic mngtmpaddr
valid_lft 6624sec preferred_lft 3024sec
inet6 fe80::be24:11ff:fe0d:f374/64 scope link
valid_lft forever preferred_lft forever
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:1b:7b:8c:1c brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:1bff:fe7b:8c1c/64 scope link
valid_lft forever preferred_lft forever
6: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:90:d8:f2:22 brd ff:ff:ff:ff:ff:ff
inet 172.30.32.1/23 brd 172.30.33.255 scope global hassio
valid_lft forever preferred_lft forever
inet6 fe80::42:90ff:fed8:f222/64 scope link
valid_lft forever preferred_lft forever
18: veth6d0965b@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 42:78:6b:fc:c2:84 brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::4078:6bff:fefc:c284/64 scope link
valid_lft forever preferred_lft forever
20: veth229babf@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default
link/ether 66:1f:19:3c:bf:84 brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::641f:19ff:fe3c:bf84/64 scope link
valid_lft forever preferred_lft forever
24: vethd6c397e@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP group default
link/ether a2:bf:2d:d3:c7:e0 brd ff:ff:ff:ff:ff:ff link-netnsid 2
inet6 fe80::a0bf:2dff:fed3:c7e0/64 scope link
valid_lft forever preferred_lft forever
It looks like everything is happening inside the docker virtual network with no connection to the outside.
What to do?
why supervised and not HA OS ?
I could not get HA OS to run in a container at all. I used the QCOW2 image as provided from the Home Assistant site, but the Proxmox ARM64 port had an issue with the Ubuntu Noble version.
If I had a standalone Raspi I would go for a native install, but unfortunately I need HA to co-exist with other containers on one…
No solution, but a ‘workaround’… I bought a second Raspi and now have installed a standalone HAOS. Rats.