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

update: LXC 300 was OpenClaw (migrated from LXC 224) - shut down intentionally

Browse Source
This commit is contained in:
Cal Corum 2026-02-19 11:16:52 -06:00
parent 355cdfa29d
commit 28c2c21b6c
1 changed files with 17 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
graph/decisions/lxc-300-claude-code-shut-down-unused-container-a9d6f7.md
View File

@ -1,31 +1,29 @@
---
id: a9d6f7a1-69d9-41ab-b28c-88f02d21a43b
type: decision
title: "LXC 300 (claude-code) shut down - unused container"
tags: [proxmox, homelab, infrastructure, cleanup]
title: "LXC 300 was OpenClaw (migrated from LXC 224) - shut down intentionally"
tags: [proxmox, homelab, openclaw, infrastructure, cleanup]
importance: 0.6
confidence: 0.8
created: "2026-02-19T17:13:31.147499+00:00"
updated: "2026-02-19T17:13:31.147499+00:00"
updated: "2026-02-19T17:16:52.507526+00:00"
---
## LXC 300 (claude-code) Shut Down (2026-02-19)
## LXC 300 Shut Down (2026-02-19) — Was Running OpenClaw
Shut down LXC 300 'claude-code' on Proxmox after determining it was unused.
LXC 300 (hostname 'claude-code') was actually running OpenClaw, migrated from LXC 224 at some unknown point. This migration was never documented.
### 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
### Evidence
- LXC 224 (openclaw-lxc) had been shut down for ~10 minutes with no Uptime Kuma alert
- As soon as LXC 300 was shut down, Uptime Kuma fired an OpenClaw Gateway down alert
- The Uptime Kuma monitor was still pointed at 10.10.0.224:18789 (old LXC)
- LXC 300 had hostname 'claude-code' which was misleading
### 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
### Actions taken
- LXC 300 shut down intentionally (OpenClaw no longer needed)
- LXC 224 also shut down (was already empty after migration)
- Uptime Kuma monitor for OpenClaw should be removed/disabled
### 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
### Recovery if needed
- Backup: /mnt/pve/home-truenas/pve7to8-backups/vzdump-lxc-300-2026_02_19-*.tar.zst
- Start: pct start 300