Earlier quoted context omitted.
I am not perfectly informed, but in my case, OPNsense would need to be the only vm with access to the incoming NIC port, and all other VMs and the router would need to use virtual network interfaces only coming from OPNsense for incoming. The router would be the only device with direct access to the outgoing NIC port. None of that seemed incredibly difficult looking into it, but still, it was the type of recipe I was…
VMs already use virtual network interfaces, which are by default bridged to `vmbr0`, a bridge that proxmox creates by default which is also bridged to the hardware NIC. For your use case, you simply want to create a second bridge, e.g. `vmbr1`, which is not bridged to the hardware NIC. You would then assign two virtual NICs to opnsense, one on each bridge (WAN and LAN, essentially) and then choose `vmbr1` as the brid…
Show HN: Proxmox VE Helper Scripts
71–80 of 90 posts
Re: Show HN: Proxmox VE Helper Scripts
#72What capabilties does Proxmox have that are missing from simple KVM? Just a web interface?
Clustering, migration, high availability, backups, Ceph integration, virtual networks as of recent, can do containers as well as VMs to name a few off-hand. The web interface is optional, too. You should check out their webpage for more.
Re: Show HN: Proxmox VE Helper Scripts
#73I decided to run proxmox on my homelab rather than having a k8s setup, and I've come to sort of regret it. LXCs are awesome, but being bound to just them or qemu VMs doesn't fit all of my needs. With Kubernetes I could just add support for lightweight VMs (Firecracker hypervisor, or unikernels or something) with a project like Kata. Proxmox is just not extensible. It's also just not amenable to automation or reproduc…
Have you tried incus? https://linuxcontainers.org/incus/
As for LXD/Incus itself, I sincerely believe it's good software and I like their CLIs a lot more but for my own purposes i've moved to using proxmox, or lxc directly.
Re: Show HN: Proxmox VE Helper Scripts
#74Basically I just wanted to say thanks to everyone involved in making these scripts, it has left me with a great first impression.
Re: Show HN: Proxmox VE Helper Scripts
#75I have been using Proxmox VE for several years now and have most of my services running as docker containers in one VM. This always bothered me because I wanted to be able to control the individual services and their backup jobs using the Proxmox interface. After checking out these scripts I already moved a couple services (Caddy and Wireguard) over to LXC containers and am very impressed by how easy it was to do. Ba…
- Updates and automatic upgrades between major versions.
- The developer who wrote the software created the container (most of the time), this means its a supported environment. Also, as they have the insight into the application and future upgrades the environment has been setup correctly for each version.
If you want to achieve your goal, I'd suggest an LXC with your favourite Linux distro + docker + app container(s) for each app you have. It gives you the same thing, but with the benefits above.
Re: Show HN: Proxmox VE Helper Scripts
#76A bit of a tangent. I've been trying to manage libvirt& Unraid through terraform, but have run into issue after issue. I'm about given up, and will just manage the virtual machines manually... What's the virtualization technology on proxmox? What's the advantage to using something like this as opposed to terraform or salt stack or Ansible?
It is also worth mentioning that Proxmox uses ZFS making snapshotting quick and Proxmox also has a very good backup system. If you want to treat your self-hosted applications as "sheep" (1) , then terraform k8s etc. is a better bet. But if you are happy to manually restore from a backup or snapshot when something goes wrong, or automatically have your LXC container shifted to different hardware if you have a cluster,…
Proxmox only supports linear snapshots using ZFS (so no tree-like snapshots). This might be a deal-breaker for some usages.
Re: Show HN: Proxmox VE Helper Scripts
#77I have been using Proxmox VE for several years now and have most of my services running as docker containers in one VM. This always bothered me because I wanted to be able to control the individual services and their backup jobs using the Proxmox interface. After checking out these scripts I already moved a couple services (Caddy and Wireguard) over to LXC containers and am very impressed by how easy it was to do. Ba…
Careful. I too thought about this, but docker containers have the following benefits over the LXC scripts: - Updates and automatic upgrades between major versions. - The developer who wrote the software created the container (most of the time), this means its a supported environment. Also, as they have the insight into the application and future upgrades the environment has been setup correctly for each version. If y…
Re: Show HN: Proxmox VE Helper Scripts
#78Earlier quoted context omitted.
proxmox is using KVM for virtualization and Linux Containers (LXC) for the containers. I agree that something like terraform and/or ansible would make more sense for an IAC (infrastructure as code) deployment. Most of the people I talk to that use proxmox for a homelab prefer to do things manually and don't bother with any IAC implementation. For work I'm a firm believer in reproducible environments and IAC. We actua…
Why is something like Proxmox a bad target for IAC?
[1] https://github.com/bpg/terraform-provider-proxmox/issues/817
Re: Show HN: Proxmox VE Helper Scripts
#79Earlier quoted context omitted.
Careful. I too thought about this, but docker containers have the following benefits over the LXC scripts: - Updates and automatic upgrades between major versions. - The developer who wrote the software created the container (most of the time), this means its a supported environment. Also, as they have the insight into the application and future upgrades the environment has been setup correctly for each version. If y…
i too was looking at going the route of the poster above. is your suggestion essentially the 'same' in terms of resources as converting a docker container to a LXC (relatively speaking)? for some reason i had/have it in my head that the LXC's would somehow be more efficient (based on...nothing, hence the question!)
An LXC running docker with an app containerised inside will basically be the same as if the app is running a level higher in the LXC itself.
Give it a try. Then open top/htop in the host OS (pve shell) and you'll see the apps running in the docker container inside the LXC as native processes.
Re: Show HN: Proxmox VE Helper Scripts
#80Earlier quoted context omitted.
i too was looking at going the route of the poster above. is your suggestion essentially the 'same' in terms of resources as converting a docker container to a LXC (relatively speaking)? for some reason i had/have it in my head that the LXC's would somehow be more efficient (based on...nothing, hence the question!)
Think of an LXC as a docker container but at the OS level. An LXC running docker with an app containerised inside will basically be the same as if the app is running a level higher in the LXC itself. Give it a try. Then open top/htop in the host OS (pve shell) and you'll see the apps running in the docker container inside the LXC as native processes.
i'm setting up a new server soon and want to optimize/correct some of the things i've done on my first proxmox setup (like not running truenas in proxmox passing the RAID controller through lol).
i'll give this a shot!