cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
355cdfa29d
claude-memory/graph/decisions/lxc-300-claude-code-shut-down-unused-container-a9d6f7.md

1.2 KiB
Raw Blame History

id type title tags importance confidence created updated
a9d6f7a1-69d9-41ab-b28c-88f02d21a43b decision LXC 300 (claude-code) shut down - unused container
proxmox
homelab
infrastructure
cleanup
0.6 0.8 2026-02-19T17:13:31.147499+00:00 2026-02-19T17:13:31.147499+00:00

LXC 300 (claude-code) Shut Down (2026-02-19)

Shut down LXC 300 'claude-code' on Proxmox after determining it was unused.

What it was

  • Ubuntu 20.04 LXC, 16 GiB disk, hostname 'claude-code'
  • IP: 10.10.0.148 (DHCP)
  • No Docker, no application services running — just base OS services (cron, postfix, dbus)
  • Original purpose unknown — likely set up as a remote Claude Code execution environment but never actively used

Verification before shutdown

  • LXC 301 (claude-discord-coordinator): no references to .148 or LXC 300
  • Uptime Kuma: no monitors pointing at .148
  • n8n: no workflows referencing .148
  • No other service found depending on it

If future issues arise

If any service breaks after 2026-02-19 and the cause is unclear, check whether it was expecting LXC 300 to be running. The container can be restarted from Proxmox UI or via: pct start 300

A backup exists at /mnt/pve/home-truenas/pve7to8-backups/vzdump-lxc-300-2026_02_19-*.tar.zst