#I used the script by tteck to create the
1 messages ยท Page 1 of 1 (latest)
I'm not a docker guy so my ability to assist is quite limited, but it does look like a permissions issue. Have you verified your permissions?
WHAT script did you use? That looks suspiciously like a Supervised install. Are you really wanting to install Supervised?
As for a supervised install, I'm open to options for best practice, my Proxmox knowledge is limited.
I don't think tteck has a supervised script. It's probably the rescue console or what you get via login.
Check journalctl -ru hassos-supervisor.
Output from journalctl -ru hassos-supervisor: https://i.imgur.com/lUspT4X.png
What does docker logs -tn 1000 hassio_supervisor say?
Aha. So apparently networking issues.
Try these
ip a
ping google.com
ping 1.1.1.1
nslookup google.com
nslookup google.com 1.1.1.1
IP: https://i.imgur.com/h9qSrCr.png
NSLOOKUPs: https://i.imgur.com/rzUhvKp.png
Looks fine to me. Maybe HAOS is having a moment. Have you tried rebooting it?
I've tried a few different times, as well as creating entirely new VMs, all yielding the same results.
I may try running it as an LXC instead of a VM and just run it inside of Docker. Should be good enough for my install.
HAOS cannot be run as CT and docker in a CT is not recommended by proxmox.
That's why I was deferring, I didn't think it was advisable either but me and docker aren't good friends so I didn't want to talk out of my butt ๐
I run HA as docker container in production too. In this case I would recommend a VM with HA as docker container and you can become friends.
HAOS becomes useful when you're not familiar with docker, don't want to replicate addons yourself or want an addon that is painful to replicate yourself such as the voice stuff.
Second vote for HA in a docker container (either inside a VM or on bare metal).
Since they already have proxmox it makes sense to use it. Just virtualizing a single VM still comes with benefits: #hardware-archived message
Oh yeah, I don't doubt you at all about the VM benefit. I just add that because people have asked why running a single container inside of a VM makes sense ๐ (and iirc, you've answered a few of those as well).
So just a basic (fill in the blank with a Linux distro) VM with Docker running on it?