NUC, Proxmox and HA (a noob seeking for help) Update (4/8/24)

how to access the NAS and HA separately from the outside knowing that my access provider does not offer a static IP and that access to each VM must be differentiated from Proxmox.

HA has add-ons for duckns and nginx-proxy-manager which should solve this... Or alternatively use those things in docker or by installing on your host OS.

is Coral really useful with 3 cameras?

Yes if you want object detection

• do you need a Coral in USB or M.2 version?

I've only used a USB, I don't know how to pass M.2 through to the VM but I'm sure theres tutorials out there if you want to.

• are there affordable NUCs with free M.2 slots?

Can't answer that one.

• won't proxmox add a layer of complexity with Coral/Frigate/a Zigbee dongle?

Yes, you'll need to know how to pass through the devices to their respective VMs.

For project A, I'd look into tailscale. I'd advise against having home assistant open to the internet otherwise.

Don't know anything about your other project, sorry.

Hi, I read your update and you're just a little behind me on the trail, so here's some breadcrumbs.

Proxmox is awesome, stop wondering and install it, it's awesome.

Ok so you can do 2 things, VM or LXC. You're wondering what the difference is.

VM is a computer

LXC is a container.

Now as far as I can tell a container is kinda like a little computer that's made to do one thing. So it needs less resources, just what it needs to do that one thing. It also needs less permissions to do that one thing, so it has less permissions.

Now Docker is a container engine. It's beautiful because you can just tell it what to make and it'll make it. If you remember what you told it, you can do it again really quickly.

Docker is also beautiful because it will run on anything. So you can make a container on a Linux machine, then make it again on a Windows machine if you remember what you told it. This is done with a bunch of text, so as long as you can save that text and get it on another machine, well you have the container again.

Not knowing this, I've been trying to make docker work in LXC containers with a bit of success and a lot of failure. I thought I could just have a bunch of cloned LXC containers with Docker on, and make a bunch of services using minimal resources.

But now I know I'm trying to run a container inside a container and that's why I'm hitting walls.

So Proxmox VMs are gonna be your friend. It will be tempting to try and migrate to containers, but as a beginner you can save a lot of headaches by making a couple of VMs and cramming a bunch of stuff on em.

This is where Docker is useful. If you use a docker hypervisor (?) app, there's Portainer for example which I use, you can just use one instance to control a bunch of other instances of Docker.

This makes it easy to try something out on a test machine, then just move it over to another machine when it's ready. The more similar the machines are, the easier the transfer. In Proxmox you can clone things, so you can make a computer, clone it, then set things up on one and move em over when they're working right, then just turn the test machine off.

So in my opinion, boot a VM of Home Assistant OS and get that working. Make another for playing with of whichever flavour you fancy. Windows, Linux, both?

Bang docker in it and have a play. I like Portainer, made Docker easier to mess with, but I like a UI. So I got Portainer working first and used that to put Docker Compose files into "Stacks" in Portainer and poked them.

Then when I found stuff I liked I tried booting them so they work, be that in a VM, and LXC or in Docker if I had got it working to my liking already. Because Docker is containers I hit a lot of problems running stuff (and I don't know what I'm doing) but found an LXC or VM easier.

Try getting piHole (and try Adguard, I prefer it) going in Docker. I found Adguard works perfectly fine in Docker, so once I got it working I just had to decide where I wanted it and ended up having an instance in Docker in an LXC (container in a container, not great, but it works.

Then I copied it onto a raspberry pi, just put Docker on it and and used the same file. That means that if I knackered up my Proxmox my internet won't go down.

Hope that helps

I have a domain I own and access through Cloudflare, but there's also DuckDNS or Nabu Casa.

Or as someone else has pointed out, Tailscale, which is awesome, and free.

That's to access from outside.

As for NAS, I'm currently happily using Open Media Vault.

won't proxmox add a layer of complexity with Coral/Frigate/a Zigbee dongle?

Nah, just pass it through

how to access the NAS and HA separately from the outside knowing that my access provider does not offer a static IP and that access to each VM must be differentiated from Proxmox.

Tailscale, it will take about 5 minutes to set up and cost nothing.

I have dynamic IP and there are several ways around it. I use Cloudflared (updates DNS records regularly) and a script I found to update duck DNS as a backup. Both very simple.

Accessing the services is not the problem, the problem is keeping them safe. I've tried lots of different ways (although not tailscale yet) and have a few services exposed directly to the internet behind authentik \ NPM \ Cloudflare \ fail2ban \ ufw. Others, I access through my router openvpn server, with keys for my laptop and phone as clients. There are so many guides online for all VPN types. Its just finding the right approach between ease of use vs safety

for ease of use i would not use a pci coral. usb just is easier. passing the usb through to a dock or vm is easier. i use unraid and it was extra work to get the pcie vs usb coral setup. I have a nuc with a bunch of ssds for this kinda thing too.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

10 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

[Thread #656 for this sub, first seen 5th Apr 2024, 09:05] [FAQ] [Full list] [Contact] [Source code]