From 480719541640b1a3fea85b551b814d50e682dde3 Mon Sep 17 00:00:00 2001 From: Lex van Roon Date: Wed, 13 Mar 2024 14:19:32 +0100 Subject: [PATCH] Add documentation about a bug we see with misp and docker --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 6e4423b..5c292ee 100644 --- a/README.md +++ b/README.md @@ -109,3 +109,15 @@ A GitHub Action builds both `misp-core` and `misp-modules` images automatically - `misp-core:${commit-sha1}[0:7]` and `misp-modules:${commit-sha1}[0:7]` where `${commit-sha1}` is the commit hash triggering the build - `misp-core:latest` and `misp-modules:latest` in order to track the latest builds available - `misp-core:${CORE_TAG}` and `misp-modules:${MODULES_TAG}` reflecting the underlying version of MISP and MISP modules (as specified inside the `template.env` file at build time) + +## Running without docker-compose + +On Ubuntu 20.04 with docker 25.0.4 an issue can happen where the workers are not restarted once they are gracefully exited. This results in a log message like the following: + +`Mar 11 13:37:42 misp01 docker[12345]: 2024-03-11 13:37:42,503 INFO spawnerr: unknown error making dispatchers for 'default_00': EACCES` + +This is caused by a bug in moby (https://github.com/moby/moby/issues/31243). A workaround for this situation is to expose a TTY to the container. This can be done in the following way: +- Run the container with the `--tty` flag +- Add the `www-data` user to the `tty` group: `usermod -G tty www-data` + +More information can be found in https://github.com/MISP/misp-docker/issues/25