diff --git a/graph/edges/fix-steamcmd-in-lxc-missing-co--RELATED_TO--proxmox-api-token-cannot-set-l-0db540.md b/graph/edges/fix-steamcmd-in-lxc-missing-co--RELATED_TO--proxmox-api-token-cannot-set-l-0db540.md
new file mode 100644
index 00000000000..ed3b88229f0
--- /dev/null
+++ b/graph/edges/fix-steamcmd-in-lxc-missing-co--RELATED_TO--proxmox-api-token-cannot-set-l-0db540.md
@@ -0,0 +1,13 @@
+---
+id: 0db54077-d3d5-4d21-b4a1-122c08b79146
+type: RELATED_TO
+from_id: 0381e6a1-d6f0-4441-9911-31b633f619c3
+from_title: "Fix: SteamCMD in LXC - Missing Config and DNS Resolution Failures"
+to_id: 83f90a8e-b4a9-4858-a273-c17dd680f3a9
+to_title: "Proxmox API token cannot set LXC feature flags on privileged containers"
+strength: 0.65
+created: "2026-03-05T03:43:52.805980+00:00"
+updated: "2026-03-05T03:43:52.805980+00:00"
+---
+
+Both document LXC-specific gotchas when setting up services on Proxmox
diff --git a/graph/fixes/fix-steamcmd-in-lxc-missing-config-and-dns-resolution-failur-0381e6.md b/graph/fixes/fix-steamcmd-in-lxc-missing-config-and-dns-resolution-failur-0381e6.md
index b69726377a2..8cb48d0de3c 100644
--- a/graph/fixes/fix-steamcmd-in-lxc-missing-config-and-dns-resolution-failur-0381e6.md
+++ b/graph/fixes/fix-steamcmd-in-lxc-missing-config-and-dns-resolution-failur-0381e6.md
@@ -6,7 +6,7 @@ tags: [steamcmd, lxc, proxmox, troubleshooting, fix, game-server, claude-home]
 importance: 0.8
 confidence: 0.8
 created: "2026-03-05T03:42:41.486706+00:00"
-updated: "2026-03-05T03:43:32.939131+00:00"
+updated: "2026-03-05T03:43:52.805980+00:00"
 relations:
   - target: 35400ae2-9029-4bdb-b135-9fbcd01892cb
     type: RELATED_TO
@@ -33,6 +33,11 @@ relations:
     direction: incoming
     strength: 0.85
     edge_id: 50cb97f4-9f73-4f55-8917-83bbcf44d817
+  - target: 83f90a8e-b4a9-4858-a273-c17dd680f3a9
+    type: RELATED_TO
+    direction: outgoing
+    strength: 0.65
+    edge_id: 0db54077-d3d5-4d21-b4a1-122c08b79146
 ---
 
 # SteamCMD in LXC — Two Key Issues and Fixes
diff --git a/graph/solutions/proxmox-api-token-cannot-set-lxc-feature-flags-on-privileged-83f90a.md b/graph/solutions/proxmox-api-token-cannot-set-lxc-feature-flags-on-privileged-83f90a.md
index 744035056bb..5c5440afb2e 100644
--- a/graph/solutions/proxmox-api-token-cannot-set-lxc-feature-flags-on-privileged-83f90a.md
+++ b/graph/solutions/proxmox-api-token-cannot-set-lxc-feature-flags-on-privileged-83f90a.md
@@ -6,12 +6,17 @@ tags: [proxmox, api, lxc, permissions, homelab, fix]
 importance: 0.7
 confidence: 0.8
 created: "2026-02-08T04:17:39.644059+00:00"
-updated: "2026-02-08T04:17:39.644059+00:00"
+updated: "2026-03-05T03:43:52.805980+00:00"
 relations:
   - target: 384eebbd-a2fd-41a5-93aa-a0f8c332686d
     type: BUILDS_ON
     direction: incoming
     strength: 0.5
+  - target: 0381e6a1-d6f0-4441-9911-31b633f619c3
+    type: RELATED_TO
+    direction: incoming
+    strength: 0.65
+    edge_id: 0db54077-d3d5-4d21-b4a1-122c08b79146
 ---
 
 The Proxmox API token (even root@pam\!tokenname) cannot set feature flags like nesting=1,keyctl=1 on privileged LXC containers. Error: '403 Forbidden: Permission check failed (changing feature flags for privileged container is only allowed for root@pam)'. Workaround: Use SSH to Proxmox host and run pct create directly instead of the API. The pct CLI running as root@pam has full permissions. This affects the proxmox_client.py create_container method when passing features parameter.