Prisma Cloud Compute: ECS Defender "Error in a Defender component." when deployed with privileged false
933
Created On 01/07/25 16:36 PM - Last Modified 02/10/26 21:22 PM
Symptom
- When deploying the ECS defender DaemonSet with "privileged": false, users may see "Error in a Defender component.":
- Other "failed" messages too appear similar to the ones listed below.
ERRO 2025-01-07T16:18:48.588 defender.go:269 Failed to fetch cluster: readlink /proc/1/root: permission denied
ERRO 2025-01-07T16:18:48.593 defender.go:283 Failed to find OS distribution info: failed to read release data file open /proc/1/root/etc/os-release: permission denied
ERRO 2025-01-07T16:18:48.636 defender.go:508 Failed to get host security options: could not open /sys/module/apparmor/parameters/enabled: readlink /proc/1/root: permission denied
ERRO 2025-01-07T16:18:48.636 defender.go:570 Failed to check for prevent compatibility failed to find host config value of CONFIG_FANOTIFY_ACCESS_PERMISSIONS: exit status 1
ERRO 2025-01-07T16:18:48.637 defender.go:825 Failed to create firewall manager: open /proc/1/root/sys/fs/cgroup/memory/ecs/db7be44845fb461b937e0c62eb1d3fbb/c4c17782ac01d5d7e78ee2f76f6346c26602b30837e859130d4bfbb621e30d94/memory.limit_in_bytes: permission denied
ERRO 2025-01-07T16:18:49.671 defender.go:1092 Failed to enable process monitoring. failed to find mnt namespace for current process: readlink /proc/1/ns/pid: permission denied
ERRO 2025-01-07T16:18:49.674 defender.go:1158 Failed to initialize networking: failed to initialize host network data readlink /proc/1/ns/net: permission denied
ERRO 2025-01-07T16:18:49.675 defender.go:1186 Failed to init filesystem monitor readlink /proc/1/ns/pid: permission deniedEnvironment
- Prisma Cloud Compute Saas version
- Prisma Cloud Compute Self-hosted version
- Orchestrator Defenders on Amazon ECS
Cause
These errors occur when privileged is set to "false" in the ecs-task.json:
"privileged": false,
Resolution
- Set privileged to "true"
- Reconfigure the service to use the new task definition revision:
"privileged": true,
Additional Information
An alternative solution is to add the below capabilities/lines to the task definition:
"linuxParameters": {
"capabilities": {
"add": [
"NET_ADMIN",
"NET_RAW",
"SYS_ADMIN",
"SYS_PTRACE",
"SYS_CHROOT",
"MKNOD",
"SETFCAP",
"IPC_LOCK"
],
"drop": []
}
},
"privileged": false,