From 553eb00e24d4950947d00815f42c743e9d44facf Mon Sep 17 00:00:00 2001
From: Sean Whalen <44679+seanthegeek@users.noreply.github.com>
Date: Fri, 11 Dec 2020 11:10:36 -0500
Subject: [PATCH] Prevent runaway mysql log

We recently ran into an issue where the mysql console output was filling up the disk with

> mbind: Operation not permitted

It turns out this is a common problem with the `mysql` docker image. This is the fix.

https://stackoverflow.com/questions/55559386/how-to-fix-mbind-operation-not-permitted-in-mysql-error-log
---
 docker-compose.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docker-compose.yml b/docker-compose.yml
index 419b2b0..659aad2 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -19,6 +19,8 @@ services:
       - "MYSQL_DATABASE=misp"
     volumes:
       - mysql_data:/var/lib/mysql
+    cap_add:
+      - SYS_NICE  # CAP_SYS_NICE Prevent runaway mysql log
 
   misp:
     image: coolacid/misp-docker:core-latest