#20 - Decommission VM 105 (docker-vpn) — reclaim 256 GB disk - claude-home

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cal/claude-home#20

cal commented

2026-04-03 01:08:16 +00:00

Owner

Context

VM 105 (docker-vpn) is stopped but still consuming 256 GB on the Proxmox LVM datastore. SSH config already marks it as # DECOMMISSIONED. If this disk is on the same datastore as production VMs, reclaiming it reduces the risk of a full-datastore hard outage.

Current State

VM: 105 (docker-vpn)
Status: stopped
Allocated: 8 vCPUs, 16 GB RAM, 256 GB disk
SSH config: marked as DECOMMISSIONED

Pre-Deletion Verification (CRITICAL)

Check Pi-hole custom DNS records for any reference to docker-vpn's IP: ssh pihole "pihole -q docker-vpn" and check /etc/pihole/custom.list
Check NPM upstreams for any proxy hosts pointing to this VM's IP: check NPM UI or API
Check Proxmox firewall rules for any references to VM 105's IP
Confirm a Proxmox backup exists for VM 105 (just in case): ssh proxmox "ls -la /var/lib/vz/dump/ | grep 105"
Check if any WireGuard/VPN configs on other hosts reference this VM

Tasks

Complete all pre-deletion verification above
If no dependencies found: ssh proxmox "qm destroy 105 --purge" (purge removes disk too)
If dependencies found: document them and decide whether to migrate the function elsewhere
Verify disk space reclaimed: ssh proxmox "lvs | grep pve" before and after
Remove the DECOMMISSIONED entry from ~/.ssh/config

Labels

infra-audit, proxmox

## Context VM 105 (docker-vpn) is **stopped** but still consuming **256 GB** on the Proxmox LVM datastore. SSH config already marks it as `# DECOMMISSIONED`. If this disk is on the same datastore as production VMs, reclaiming it reduces the risk of a full-datastore hard outage. ## Current State - **VM**: 105 (docker-vpn) - **Status**: stopped - **Allocated**: 8 vCPUs, 16 GB RAM, 256 GB disk - **SSH config**: marked as DECOMMISSIONED ## Pre-Deletion Verification (CRITICAL) - [ ] Check Pi-hole custom DNS records for any reference to docker-vpn's IP: `ssh pihole "pihole -q docker-vpn"` and check `/etc/pihole/custom.list` - [ ] Check NPM upstreams for any proxy hosts pointing to this VM's IP: check NPM UI or API - [ ] Check Proxmox firewall rules for any references to VM 105's IP - [ ] Confirm a Proxmox backup exists for VM 105 (just in case): `ssh proxmox "ls -la /var/lib/vz/dump/ | grep 105"` - [ ] Check if any WireGuard/VPN configs on other hosts reference this VM ## Tasks - [ ] Complete all pre-deletion verification above - [ ] If no dependencies found: `ssh proxmox "qm destroy 105 --purge"` (purge removes disk too) - [ ] If dependencies found: document them and decide whether to migrate the function elsewhere - [ ] Verify disk space reclaimed: `ssh proxmox "lvs | grep pve"` before and after - [ ] Remove the DECOMMISSIONED entry from `~/.ssh/config` ## Labels `infra-audit`, `proxmox`

cal added the

labels 2026-04-03 01:10:16 +00:00

cal referenced this issue

2026-04-03 01:14:00 +00:00

Evaluate VM 110 (discord-bots) for decommission — now empty #32

cal referenced this issue from a commit

2026-04-03 02:32:43 +00:00

chore: decommission VM 105 (docker-vpn) — reclaim 256 GB disk (#20)

cal referenced a pull request that will close this issue

2026-04-03 02:32:57 +00:00

chore: decommission VM 105 (docker-vpn) — reclaim 256 GB #37

2026-04-03 04:58:01 +00:00