retrodaredevil

@retrodaredevil@lemmy.world

• ⁨Comment⁩ on ⁨Feedback on Network Design and Proxmox VM Isolation⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  Yup. It works pretty well for me. Just will likely have to increase the default address pool in daemon.json if you go all out.

• ⁨Comment⁩ on ⁨Feedback on Network Design and Proxmox VM Isolation⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I’m not knowledgeable on communication between VMs and how to best restrict communication there, but I have tried to make my docker networks more secure.

  I went a bit overkill for my reverse proxy and all the docker networks it’s connected to. For each service I want to expose through my reverse proxy, I manage a network specifically for that service in my caddy docker compose file. I then refer to that external network in my servjce’s docker compose file, so that caddy can access it. For example, caddy is on caddy_net-grafana and on caddy_net-homepage. Grafana and homepage are on those networks respectively. So with this setup, caddy can talk to Grafana and homepage, but Grafana and homepage cannot talk to each other.

  It wasn’t too bad to setup. I made my own conventions for keeping it manageable and it works for me. I did run into the problem where I had to increase the default subnet pool, as after you create like 30 or 31 networks there aren’t any subnets left to give out to new docker networks.

• ⁨Comment⁩ on ⁨Home Asistant on Proxmox running ZFS Raid1⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I did something similar a while back and this tutorial helped me: kb.vander.host/…/how-to-import-a-qcow2-file-to-pr…

  I think the import command it has you run allows you to import it however you want. It’s my understanding that after you import it, it’s no longer using the qcow2 file as the backing drive.