PebbleRack

Guide 09 of 25 · beginner

Choose Proxmox VE or Plain Linux for Your Lab

Pick a host operating system based on the workloads and recovery work you actually need.

Source-verified · Not lab-testedOfficial sources checked 2026-09-29. No PebbleRack hardware compatibility claim.

Outcome

You will have a written reason to use either Proxmox VE or a conventional Linux installation on an existing, compatible lab computer. This is a choice guide, not an installation or a claim that any planned PebbleRack device supports Proxmox.

Before you start

List your intended workloads, their operating systems, whether you need to isolate experiments from one another, and the data you cannot afford to lose. Confirm the hardware's architecture and virtualization features against Proxmox's current requirements. The exercises in this track assume a supported x86-64 machine with suitable firmware virtualization support. Proxmox now also documents a limited arm64 path, but these instructions have not been validated for it. Reserve a second device or external store for backups.

Steps

  1. Compare the alternatives honestly. Proxmox is useful when you need multiple VMs or containers, guest lifecycle controls, and scheduled guest backups from one host. Plain Ubuntu or another Linux distribution with Docker can be enough for a small set of trusted Linux services, with fewer layers to learn. A managed cloud service can spare you local power, hardware repair, and some infrastructure maintenance, though it brings ongoing charges, provider dependence, and data-location choices. The right answer depends on workload, budget, time, and control; none requires buying a new machine.
  2. Name reasons to avoid a local hypervisor. Do not add one if this is your only computer, you cannot maintain an off-host backup, power or internet reliability is inadequate for the intended service, physical space or noise is a problem, or you need a service available when the home network is down. A single Proxmox node is still one failure domain. If all you need is one app, a full host and guest stack may add work without benefit.
  3. Start with one job. If the computer only runs one Linux service and you are comfortable administering it directly, plain Linux is the simpler starting point. If you want several independently managed operating systems, disposable experiments, or guest-level backup and restore, evaluate Proxmox VE.
  4. Decide the isolation boundary. A VM runs a guest operating system on virtual hardware. An LXC container uses the host Linux kernel. Proxmox explicitly says full VMs generally provide better isolation for unknown or untrusted users. Choose a VM for an untrusted workload or a different kernel. Choose a container only when shared-kernel operation fits.
  5. Check operational cost. You will need update windows, backup storage, restores, monitoring, and a way to regain access if networking changes fail. Write down who will perform those tasks and how often.
  6. Choose a reversible first experiment. If uncertain, use a spare x86-64 computer. Do not repartition your only working system. Record a result that would justify keeping the platform: for example, two isolated guests and a successful restore.
  7. Record the decision. Note host, workloads, isolation, backup destination, recovery method, and the reason for the choice. If plain Linux or cloud wins, return to this track only when its features are needed.

Check it worked

You can explain why each proposed workload will run on the host, in a VM, or in a container. You have a backup destination outside the machine and know whether this project is a trial or a service you will depend on.

If it fails or rollback

If the requirements are unclear, postpone installation and inventory the hardware first. Changing this decision later can require reinstalling the host and migrating data, so keep current services and their backups intact until a test migration succeeds.

Safety and data notes

Neither Proxmox nor Linux automatically protects against drive loss, accidental deletion, or a bad update. Snapshots and local copies are not substitutes for an independently stored, restorable backup. Do not put secrets in screenshots or shared configuration notes.

Sources

Official Proxmox documentation checked 2026-09-29: installation and requirements, VMs, containers and security considerations, backup and restore.

Next guide

If you chose Proxmox and have a spare supported target, continue with guide 10, Install Proxmox VE.