Proxmox Virtualization Lab
A single-node Proxmox VE lab used to practice virtualization, Linux container administration, NAS-backed storage, static IPv4 networking, infrastructure troubleshooting, automation, and self-hosted services.
Project Goal
The goal of this lab is to build and maintain a realistic infrastructure environment where I can safely test, troubleshoot, document, and improve systems administration skills 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 lab for LXC container workloads and 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
The lab currently focuses on lightweight Linux containers instead of full virtual machines to reduce overhead and keep services isolated.
Networking
Bridge-based networking with static IPv4 addressing for lab services. IPv6 is controlled or disabled where appropriate for predictable service behavior.
Containerized Services
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.
- Used the lab to practice repeatable documentation, service isolation, troubleshooting, and infrastructure hardening.
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.
- Lab services are separated by container to limit blast radius and simplify 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 lab demonstrates hands-on infrastructure experience beyond help desk work: virtualization administration, Linux container management, storage integration, DNS and network troubleshooting, secure service publishing, automation practice, and operational documentation.
Project Status
Active and continuously improving. Future work may include better monitoring, additional automation, backup validation documentation, service diagrams, and deeper project writeups for each major lab service.