ISO installer
Use when you want to boot a machine or VM into the installer and deploy Beagle OS onto local storage.
- Best for bare-metal rollout
- Carries the installer flow
- Pairs with VM-specific preset data
Beagle OS images are served from your own Proxmox host after setup. The control plane generates VM-specific artifacts and USB scripts directly from the host that owns the target VM.
Choose the image that matches how you want to test, install, or mass-provision endpoints.
Use when you want to boot a machine or VM into the installer and deploy Beagle OS onto local storage.
Use when you want a direct-flash artifact for repeatable endpoint media creation without a separate installer session.
Use to test the endpoint OS inside a VM before you touch physical hardware or before you validate a release.
Clone the repository and run the host setup on the Proxmox node that should own the Beagle control plane.
git clone https://github.com/meinzeug/beagle-os.git
cd beagle-os
./scripts/setup-proxmox-host.sh
INSTALL_DIR=/opt/beagle
PVE_DCV_PROXY_SERVER_NAME=srv.example.net
PVE_DCV_PROXY_LISTEN_PORT=8443
BEAGLE_SITE_PORT=443
Beagle keeps provisioning VM-centric. You do not create a generic endpoint and later decide where it should connect.
| Component | Requirement |
|---|---|
| Proxmox VE | 7.x minimum, 8.x recommended |
| Endpoint memory | 2 GB minimum, 4 GB recommended |
| Endpoint storage | 8 GB USB minimum, 16 GB SSD recommended |
| Network | 100 Mbit LAN minimum, Gigabit recommended |
| VM GPU | Any GPU, NVIDIA with NVENC recommended |
Artifacts are published by your own Proxmox host after setup. Verify checksums directly on the host before you distribute images.
cd ${INSTALL_DIR:-/opt/beagle}/dist
sha256sum beagle-os-installer-amd64.iso
sha256sum pve-thin-client-usb-bootstrap-latest.tar.gz
The generated USB scripts download the matching payload from the same host, so the checksum you verify is the checksum your endpoint media uses.