cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
33a40f992a
claude-memory/graph/solutions/docker-in-lxc-requires-apparmor-unconfined-on-proxmox-384eeb.md
Cal Corum b140d4d82a migrate: 313 memories from MemoryGraph 
- 313 new markdown files created
- 30 relationships embedded
- 313 entries indexed
- State initialized with usage data
2026-02-13 11:11:48 -06:00

1.0 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-02-08T04:17:35.578335+00:00
target type direction strength
83f90a8e-b4a9-4858-a273-c17dd680f3a9 BUILDS_ON outgoing 0.5

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.