From 6242cc5f31ab7ae9e2e9abf27c3128a618e0e01c Mon Sep 17 00:00:00 2001 From: Rich Date: Thu, 14 Sep 2023 15:25:35 +0200 Subject: [PATCH] Move how-to on fixing container starting to project repo If you're reading this trying to figure out why this link doesn't work, maybe the [pull request](https://github.com/mu-semtech/project/pull/5) hasn't been merged yet. In which case, you want to look here: https://github.com/Denperidge-Redpencil/docs-update-project/blob/master/docs/how-tos/troubleshooting---slow-starting-containers.md --- README.md | 27 +-------------------------- 1 file changed, 1 insertion(+), 26 deletions(-) diff --git a/README.md b/README.md index cda8b00..6498bc5 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ Setting up your environment is done in three easy steps: 3. Lastly, simply start the docker-compose. > [!WARNING] -> Many of the containers used have issues with high limits on open file descriptors, so you might need [to work around this](#containers-stuck-while-starting-using-100-cpu) +> Many of the containers used have issues with high limits on open file descriptors, so you might need [to work around this](https://github.com/mu-semtech/project/blob/master/docs/how-tos/troubleshooting---slow-starting-containers.md) #### Hooking things up with docker-compose @@ -36,28 +36,3 @@ You can shut down using `docker-compose stop` and remove everything using `docke To help you find your feet with your first semantic works projects, we've collected [a few tutorials](TUTORIALS.md). -## Troubleshooting - -### Containers stuck while starting, using 100% CPU -Some docker images used in mu-project, notably those based on sbcl (lisp) and elixir images, are very slow and CPU intensive to start if the limits of open file descriptors are very high for the container. This leads to a process using 100% of a CPU for some time before that container becomes usable. This can be worked around by setting the defaults for new containers in the docker daemon config (/etc/docker/daemon.json (create it if it doesn't exist)): - -```json -{ - "default-ulimits": { - "nofile": { - "Hard": 104583, - "Name": "nofile", - "Soft": 104583 - } - } -} -``` - -Or, if you want these high defaults for some reason, you can set per-container limits in a docker-compose file for each of the mu-project services: - -```yml - ulimits: - nofile: - soft: 104583 - hard: 104583 -```