Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

My journalctl logs get spammed with apparmor messages #55

Closed
francislavoie opened this issue Nov 6, 2017 · 3 comments
Closed

My journalctl logs get spammed with apparmor messages #55

francislavoie opened this issue Nov 6, 2017 · 3 comments

Comments

@francislavoie
Copy link

I get a ton of these (like 50 per second or something, pretty nuts)

audit[13902]: AVC apparmor="DENIED" operation="ptrace" profile="docker-default" pid=13902 comm="apps.plugin" requested_mask="trace" denied_mask="trace" peer="unconfined"

This is my docker-compose.yml:

netdata:
    image: titpetric/netdata:1.8
    expose:
        - "19999"
    volumes:
        - /proc:/host/proc:ro
        - /sys:/host/sys:ro
        - /var/run/docker.sock:/var/run/docker.sock
    environment:
        NETDATA_PORT: 19999
    cap_add:
        - SYS_PTRACE

That pid is the /usr/libexec/netdata/plugins.d/apps.plugin 1 command/process.

This is probably an apparmor misconfiguration, but I have no idea where to look to solve this, so I thought I'd ask for help.

Thanks

@titpetric
Copy link
Owner

titpetric commented Nov 19, 2017

Try adding --security-opt apparmor:unconfined or whatever the compose.yml equivalent of that would be. Referenced in moby/moby#7276, closing because it's a sysadmin issue, not a container/netdata issue.

@nemchik
Copy link

nemchik commented Sep 3, 2018

This is what you need for docker-compose

    security_opt:
      - apparmor:unconfined

@folex
Copy link

folex commented May 15, 2019

Hi! Is there any way to disable that behaviour in netdata if I don't want to allow ptrace in my containers?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants