cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
03e096949f
claude-memory/graph/solutions/docker-in-lxc-requires-apparmor-unconfined-on-proxmox-384eeb.md
Cal Corum 03e096949f relate: ccb2b5a4 --RELATED_TO--> 384eebbd
2026-03-04 21:43:47 -06:00

1.2 KiB
Raw Blame History

id type title tags importance confidence created updated relations
384eebbd-a2fd-41a5-93aa-a0f8c332686d solution Docker-in-LXC requires AppArmor unconfined on Proxmox
proxmox
docker
lxc
apparmor
homelab
fix
0.8 0.8 2026-02-08T04:17:35.578335+00:00 2026-03-05T03:43:47.041443+00:00
target type direction strength
83f90a8e-b4a9-4858-a273-c17dd680f3a9 BUILDS_ON outgoing 0.5
target type direction strength edge_id
ccb2b5a4-a9bb-4f8f-9367-d74713ab2415 RELATED_TO incoming 0.7 45b41b28-79e7-4b61-a2e5-10d75dd7e248

When creating a Proxmox LXC container to run Docker, the container needs AppArmor set to unconfined. Without this, Docker containers fail to start with: 'AppArmor enabled on system but the docker-default profile could not be loaded'. Fix: Stop LXC, append to /etc/pve/nodes/proxmox/lxc/.conf: lxc.apparmor.profile: unconfined, lxc.cgroup2.devices.allow: a, lxc.cap.drop: (empty). Also need features: nesting=1,keyctl=1 for Docker support. Note: Proxmox will warn 'explicitly configured lxc.apparmor.profile overrides the following settings: features:nesting' but this is harmless and Docker works correctly.