cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

store: discord-bots VM (10.10.0.33) - all containers stopped, flagged for decommission

Browse Source
This commit is contained in:
Cal Corum 2026-02-20 11:09:44 -06:00
parent 646b2f5315
commit 28519c58fd
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
graph/configurations/discord-bots-vm-1010033-all-containers-stopped-flagged-for-d-6400cc.md Normal file
View File

@ -0,0 +1,30 @@
---
id: 6400ccf0-b268-4342-9a13-6157cfc8fc03
type: configuration
title: "discord-bots VM (10.10.0.33) - all containers stopped, flagged for decommission"
tags: [proxmox, homelab, cleanup, infrastructure, discord-bots, decommission]
importance: 0.6
confidence: 0.8
created: "2026-02-20T17:09:44.301102+00:00"
updated: "2026-02-20T17:09:44.301102+00:00"
---
# discord-bots VM (10.10.0.33) - Decommission Status
## VM Details
- **IP:** 10.10.0.33
- **OS:** Ubuntu desktop (GNOME, CUPS)
- **Total containers:** 12 (all now stopped/exited)
## Actions Taken
- Stopped `foundry_foundry_1` and `mln-ghost-ball_discord-app_1` — neither was in production use
- Added CT 302 public key to `authorized_keys` for future access
- Skipped adding to health monitoring (nothing active)
- **Flagged for full decommission** on next Proxmox cleanup pass
## Important Note
Foundry VTT **production** instance is on `foundry-lxc` (10.10.0.223), NOT this VM. Do not confuse the two.
## Next Steps
- Review during next Proxmox cleanup pass for full VM removal
- All 12 containers are stopped — safe to decommission when ready