• 1 Post
  • 501 Comments
Joined 5 months ago
cake
Cake day: August 25th, 2025

help-circle
  • LXC is more focused on the OS than the application, where docker is more focused in the application. In general, I don’t recommend piping to bash, but take a look here for some lxc build scripts:

    https://community-scripts.github.io/ProxmoxVE/

    And you can still run docker with proxmox. You can make a VM and put docker in it, or you can run it in an LXC.

    Regarding VMs, that’s purely an example of how I am doing things, and only for specific things. I start and stop VMs because I’m passing specific hardware (a discrete GPU) to the VM, its not a shared resource in this case. I’m not making a virt GPU, the VM gets to use the quadro that’s in there directly. I have other VMs (HomeAssistantOS for example) that run all the time.

    LXC can be used to share resources with a host. VMs can be used to dedicate resources. LXCs are semi-isolated, and a VM is fully isolated.

    My example of the iGPU/dGPU is because of my use cases, nothing more.

    Clustering is easy and can be done over time. Your new host needs to join the existing server before adding any VMs or LXCs, that’s about it. A good overview of how to do it is here:

    https://www.wundertech.net/how-to-set-up-a-cluster-in-proxmox/









  • My setup doesnt matter, I don’t use Unifi for my main home infra.

    You can use the Unifi device itself. Teleport is just a single click Wireguard service, with no need for port forwarding or additional configuration.

    Last I saw it, you can export the config from the browser for use with client devices, you can use that with wireguard tunnel and set it as always on.


  • I am, though I’m not using unifi.

    Teleport is just Wireguard with unifi stacked on top. You can just export the config and its literally a Wireguard connection. Unifi Teleport is just using their online services to replace a step.

    But teleport (which is Wireguard under the hood) is not meant for an always-on connection, its meant for ad-hoc connections.

    So if you want always on, export the config and run it as a Wireguard tunnel. Its exactly the same service, running on exactly the same device, without using wifiman and allowing for an always on VPN.








  • curbstickle@anarchist.nexustoLinux@lemmy.mlReplace Windows, Excel needed
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    8 days ago

    If its for work, its on a work machine.

    That said, I have a lot of efforts (personal projects with hardware I get given, or side work not related to my job) where I need specific software. For those, I have a VM tailored to that application that’s been trimmed down as much as possible.

    This let’s me rdp into them, do what I need to do, save to a designated location, and shut the VM down. Since its a VM I tend not to give it network access unless required, and I have USB drive I pass through to the VM.

    This makes sure everything works, I limit the access of MS with local only accounts and win 10 (among other specific versions like XP for a specific piece of hardware, server 2008 for an irritating piece of software I sometimes need, etc).

    All the VMs are on my proxmox cluster, easy to start/stop with a script.