Limitations of Docker Ambassador? Syslog on other Docker machine filling up quickly

I have ElasticSearch & RabbitMQ Docker with Ambassador on one machine and then Storm Docker container on the other machine.

My kern.log is filling up quickly on the machine with statements like this

  • Docker exec - Write text to file in container
  • How to downgrade docker on CoreOS?
  • AWS Discovery only tries 3 ports 5701, 5702 & 5703 while joining cluster
  • I run the docker images which start tomcat8 server but it don't start
  • Gitlab & Mattermost OAUTH Time out
  • Is docker a solution for making application cross platform?
  • /var/log/kern.log shows lots of the following messages:kernel: [88830.564267] type=1400 audit(1411850795.721:143275): apparmor=”DENIED” operation=”ptrace” profile=”docker-default” pid=19623 comm=”busybox” requested_mask=”trace” denied_mask=”trace” peer=”docker-default”

    Busybox seems to be part of Docker and the Storm machine seems to be expecting some security threat and it is logging that.

    What precautions should be taken while setting ambassador up on any machine that has Dockers?

  • amazon beans talk docker Failed to build Docker image aws_beanstalk/staging-app not a directory
  • Docker plugin : /src/main/docker/Dockerfile gradle-docker fails
  • Nightwatch keeps giving 502 bad gateway
  • Kafka on Kubernetes multi-node
  • docker cp the content of a folder
  • Is it possible to mount a volume on the host during BUILD phase of a docker image?
  • One Solution collect form web for “Limitations of Docker Ambassador? Syslog on other Docker machine filling up quickly”

    I presume that this is related to

    (as the log file says, your AppArmor profile is denying trace access.)

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.