Skip to content

Commit 6242cc5

Browse files
committed
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](mu-semtech/project#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
1 parent 239d36c commit 6242cc5

File tree

1 file changed

+1
-26
lines changed

1 file changed

+1
-26
lines changed

README.md

Lines changed: 1 addition & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Setting up your environment is done in three easy steps:
1313
3. Lastly, simply start the docker-compose.
1414

1515
> [!WARNING]
16-
> 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)
16+
> 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)
1717
1818
#### Hooking things up with docker-compose
1919

@@ -36,28 +36,3 @@ You can shut down using `docker-compose stop` and remove everything using `docke
3636

3737
To help you find your feet with your first semantic works projects, we've collected [a few tutorials](TUTORIALS.md).
3838

39-
## Troubleshooting
40-
41-
### Containers stuck while starting, using 100% CPU
42-
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)):
43-
44-
```json
45-
{
46-
"default-ulimits": {
47-
"nofile": {
48-
"Hard": 104583,
49-
"Name": "nofile",
50-
"Soft": 104583
51-
}
52-
}
53-
}
54-
```
55-
56-
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:
57-
58-
```yml
59-
ulimits:
60-
nofile:
61-
soft: 104583
62-
hard: 104583
63-
```

0 commit comments

Comments
 (0)