Proxmox Virtualization Lab
A single-node Proxmox VE infrastructure environment used to host and administer Linux containers, virtual machines, NAS-backed storage, static IPv4 networking, automation, monitoring, and self-hosted services.
Project Goal
The goal of this environment is to maintain a realistic infrastructure platform for deploying services, troubleshooting systems, validating changes, documenting configurations, and developing repeatable administration practices outside of production client networks.
Public-facing documentation intentionally avoids publishing internal IP addresses, storage paths, hostnames, MAC addresses, tunnel identifiers, or other private lab details.
Current Lab Snapshot
Virtualization Platform
Proxmox VE 9.2 running as a single-node virtualization platform for dedicated LXC service workloads, virtual machines, and controlled infrastructure testing.
Storage
Combination of local Proxmox storage and NFS-backed NAS storage for container disks, templates, backups, ISO images, and lab file storage.
Container Workload Layout
Most persistent services run in dedicated Linux containers to reduce overhead, separate workloads by function, and simplify maintenance and troubleshooting. Virtual machines are used where a full guest operating system or appliance-style deployment is appropriate.
Networking
Bridge-based networking with static IPv4 addressing for lab services. IPv6 is controlled or disabled where appropriate for predictable service behavior.
Hosted Services and Workloads
The lab uses dedicated containers to separate services by function. Current workloads include:
- Cloudflare Tunnel connector for secure service publishing.
- Nextcloud for self-hosted cloud storage and service testing.
- Pi-hole for DNS filtering, domain review, and network visibility.
- PDF utility services for document handling and workflow testing.
- Docker services host for containerized workloads and service experiments.
- Ansible management environment for configuration management practice.
- Portfolio web container running this public technical portfolio.
- Additional stopped lab services retained for future testing and rebuild practice.
Architecture
Technologies Used
Administrative Work Performed
- Created and organized multiple Linux containers for separate infrastructure roles.
- Configured static IPv4 addressing for predictable service access and troubleshooting.
- Controlled or disabled IPv6 where needed to reduce unwanted auto-assignment and simplify service behavior.
- Integrated NAS-backed storage into Proxmox for templates, backups, container data, and lab files.
- Configured and tested container network behavior across the bridge interface.
- Deployed self-hosted services and validated access through local network paths and Cloudflare Tunnel routes.
- Maintain repeatable documentation, workload separation, troubleshooting procedures, and infrastructure hardening across the environment.
Security and Privacy Considerations
- Internal IP addresses and exact hostnames are not published on the public project page.
- Public access to selected services is handled through Cloudflare Tunnel instead of direct port forwarding.
- Services are separated by workload to reduce unintended cross-service impact and simplify maintenance and troubleshooting.
- Firewall rules are used to limit unnecessary access to public-facing workloads.
- Service documentation is sanitized before being published publicly.
What This Demonstrates
This environment demonstrates hands-on infrastructure administration across virtualization, Linux workload management, storage integration, DNS and network troubleshooting, secure service publishing, automation, monitoring, and operational documentation.
Project Status
Active and continuously maintained. Core services remain in use, while completed or temporary workloads may be stopped when they are no longer needed. Ongoing work focuses on automation, monitoring, backup validation, documentation, and controlled service expansion.