cal/claude-home
1
0
Fork 0
Code Issues 6 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Right-size VM 106 (docker-home): 16 GB → 6-8 GB RAM #19

New Issue
Open
opened 2026-04-03 01:08:05 +00:00 by cal · 1 comment
cal commented 2026-04-03 01:08:05 +00:00
Owner
Copy Link

Context

Infrastructure audit (2026-04-02) found VM 106 (docker-home) has 16 GB RAM allocated but only 1.5 GB in use. This is 10x overprovisioned.

Current State

  • VM: 106 (docker-home)
  • Allocated: 8 vCPUs, 16 GB RAM
  • Actual usage: 1.5 GB RAM, load 0.12/core
  • Services: Pi-hole, Nginx Proxy Manager, Portainer (only ~900 MB combined)

Tasks

  • Verify no Docker containers on this VM have --memory limits that would cause OOM issues at lower RAM
  • Check Docker Compose files for any memory reservations: grep -r memory /home/cal/docker-*/docker-compose.yml or similar
  • Shut down VM (schedule maintenance — Pi-hole and NPM will be briefly down; manticore Pi-hole provides HA DNS)
  • Reduce RAM from 16 GB to 6 GB (4x current usage = safe headroom)
  • Also consider reducing vCPUs from 8 to 4 (load is 0.12/core)
  • Start VM and verify all services: Pi-hole DNS resolution, NPM proxy routes, Portainer UI
  • Monitor for 24h — check if memory usage stays well below 6 GB

SRE Notes

  • Pi-hole and NPM are critical services — manticore runs a secondary Pi-hole for HA DNS, so brief downtime is survivable
  • 6 GB gives 4x headroom over current 1.5 GB usage
  • NPM can spike memory under heavy proxy load but unlikely to exceed 4 GB

Labels

infra-audit, proxmox

## Context Infrastructure audit (2026-04-02) found VM 106 (docker-home) has **16 GB RAM allocated** but only **1.5 GB in use**. This is 10x overprovisioned. ## Current State - **VM**: 106 (docker-home) - **Allocated**: 8 vCPUs, 16 GB RAM - **Actual usage**: 1.5 GB RAM, load 0.12/core - **Services**: Pi-hole, Nginx Proxy Manager, Portainer (only ~900 MB combined) ## Tasks - [ ] Verify no Docker containers on this VM have `--memory` limits that would cause OOM issues at lower RAM - [ ] Check Docker Compose files for any memory reservations: `grep -r memory /home/cal/docker-*/docker-compose.yml` or similar - [ ] Shut down VM (schedule maintenance — Pi-hole and NPM will be briefly down; manticore Pi-hole provides HA DNS) - [ ] Reduce RAM from 16 GB to **6 GB** (4x current usage = safe headroom) - [ ] Also consider reducing vCPUs from 8 to 4 (load is 0.12/core) - [ ] Start VM and verify all services: Pi-hole DNS resolution, NPM proxy routes, Portainer UI - [ ] Monitor for 24h — check if memory usage stays well below 6 GB ## SRE Notes - Pi-hole and NPM are critical services — manticore runs a secondary Pi-hole for HA DNS, so brief downtime is survivable - 6 GB gives 4x headroom over current 1.5 GB usage - NPM can spike memory under heavy proxy load but unlikely to exceed 4 GB ## Labels `infra-audit`, `proxmox`
cal added the
infra-audit
proxmox
 labels 2026-04-03 01:10:15 +00:00
Claude added the
ai-working
 label 2026-04-04 04:00:50 +00:00
Claude removed the
ai-working
 label 2026-04-04 04:06:11 +00:00
Claude commented 2026-04-04 04:06:18 +00:00
Collaborator
Copy Link

Pre-checks completed, config updated, runbook created — PR #47 ready for review.

Verification findings:

  • No container --memory limits (all MemoryLimit: 0) — no OOM risk at 6 GB
  • No Docker Compose memory reservations in any compose files
  • Live usage: 1.1 GB / 15 GB (Pi-hole 463 MiB + NPM 367 MiB + Portainer 12 MiB)

Changes in the PR:

  • server-configs/proxmox/qemu/106.conf: memory 16384 → 6144, sockets 2 → 1 (8 → 4 vCPUs)
  • server-configs/proxmox/right-sizing-vm-106.md: runbook with resize commands, validation steps, and rollback

The actual Proxmox resize still needs to be executed manually — see the runbook for the 3-command procedure. Brief Pi-hole/NPM downtime; manticore Pi-hole 2 covers DNS.

Pre-checks completed, config updated, runbook created — PR #47 ready for review. **Verification findings:** - No container `--memory` limits (all `MemoryLimit: 0`) — no OOM risk at 6 GB - No Docker Compose memory reservations in any compose files - Live usage: 1.1 GB / 15 GB (Pi-hole 463 MiB + NPM 367 MiB + Portainer 12 MiB) **Changes in the PR:** - `server-configs/proxmox/qemu/106.conf`: `memory 16384 → 6144`, `sockets 2 → 1` (8 → 4 vCPUs) - `server-configs/proxmox/right-sizing-vm-106.md`: runbook with resize commands, validation steps, and rollback The actual Proxmox resize still needs to be executed manually — see the runbook for the 3-command procedure. Brief Pi-hole/NPM downtime; manticore Pi-hole 2 covers DNS.
Claude added the
ai-pr-opened
 label 2026-04-04 04:06:21 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
ai-changes-requested

   
ai-failed

   
ai-pr-opened

   
ai-reviewed

   
ai-reviewing

   
ai-working

   
infra-audit

Infrastructure audit remediation tasks

  
monitoring

Monitoring, alerting, and observability

  
operations

Ongoing operational improvements

  
proxmox

Proxmox VM/CT management

  
script

Script improvements and tooling

No Label
ai-changes-requested
ai-failed
ai-pr-opened
ai-reviewed
ai-reviewing
ai-working
infra-audit
monitoring
operations
proxmox
script
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 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#19
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?