WOPR

WOPR
Name	WOPR
Zone	Infrastructure
Owner	i3Detroit
Make Model
Part Number
Date Acquired	2026-05-02
Storage Location	Media Lab cabinet rack
Authorization Required	Yes
Status	Running
Value	3550
MAC Address	a0:36:9f:7a:e8:a6/varies
Hostname	wopr.i3.lc
Power Requirements	~100W, 120VAC
Documentation
Other References

Intro

The new server, successor to Hardac, running most of the core LAN-only infrastructure of the space. The specs are:

• Motherboard: Asus PRIME B550-PLUS AC-HES
• CPU: AMD Ryzen 7 5800XT, 8-Core
• GPU: MSI/Nvidia RTX 5060 Ti 12GB
• RAM: V-Color DDR4-2666 ECC 4x16GB
• SSD: Intel 660P M.2 NVMe 2x1TB (ZFS Mirror)
• HDD: Seagate Ironwolf 4x12TB (ZFS RAIDZ2)
• NIC: Intel X540-AT2 Dual 10G Ethernet
• PSU: Sliverstone Extreme 1200R Platinum

Rules

Ask for an account if you think you need one, but chances are you actually want an account on one of the services the machine runs instead.

Instructions

The host is running Proxmox as the hypervisor. Access its HTTPS web UI through port 8006 or SSH on port 22.

Virtual Machines

When setting up new VMs, keep to the following guidelines:

• Don't create a VM unless you have to. Most services are set up in Docker.
• Put your VM OS disk onto local-zfs, the NVMe RAID, for speed. If you need more space, add it as a secondary disk.

Docker Containers

When setting up new services, keep to the following guidelines:

• Use Docker Compose, not docker run for consistency.
• Set a restart policy of unless-stopped (or always), assuming you want them to automatically start along with the host.
• Use relative paths unless you're referencing OS resources.
• If you're mounting volumes, use user/group docker-user for them

Maintenance Info

Create backups and keep things updated and working.

Hypervisor

Authorizing New Users

You probably don't need a user on the hypervisor, but if you insist:

In the web UI, visit Datacenter > Users > Add. Follow the prompts to add a user to the PAM realm. Then, in the host shell, run:

adduser example
usermod -aG sudo example

When prompted, enter the user's name in the name field, leave phones blank, and put email in other. Repeat these commands in any VMs/LXCs you want to grant access to.

LXCs

Externally Mounting The Filesystem

If for debugging purposes you need to mount an LXC disk into the hypervisor itself, you can use:

sudo pct mount <vmid>
sudo pct unmount <vmid>

Beware that unprivileged LXCs use a different band of uid/gids than the host for security reasons, and the resulting permissions issues cannot usually be remedied inside the container.

ToDo

• Create a repo for Docker Compose configs

Authorized Users and Trainers

Trainer Name	Certified Date
Ivy	2026-05-02
Mara Furland	2026-05-02

User Name	Authorized By	Date of Most Recent Training
AstraLuma	Ivy	2026-06-03

Related Files

• Equipment QR Code Label

Services

Name	Type	Hostname	IP	Ports	Description
docker-compose	LXC	docker-compose.i3.lc	10.13.0.31	SSH	Debian host for Docker
└ caddy	Docker	varies	n/a	HTTPS	Reverse proxy and ACME forwarding
└ copyparty	Docker	files.i3.lc via Caddy	n/a	HTTPS/WebDAV via Caddy	Space-wide fileserver
└ door-management	Docker	doors.i3.lc via Caddy	n/a	n/a	Updates and logs door RFID data
home-assistant	VM	ha.i3.lc	10.13.0.32	HTTPS, SSH	Home Assistant OS
vicky	LXC	vicky.i3.lc	10.13.0.33	InfluxDB, SSH	Debian host for VictoriaMetrics/observability platforms
frigate	LXC	frigate.i3.lc	10.13.0.34	HTTPS, SSH	Debian host for NVR system for cameras