> For the complete documentation index, see [llms.txt](https://iddynamics.gitbook.io/flepimop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://iddynamics.gitbook.io/flepimop/how-to-run/common-errors.md).
# Common errors
Common error messages and how to debug them
### Docker Issues
Docker Issues - storage full
* Storage full on submission box
* there can be so many error patterns in shortage of storage
{% code title="Add error" overflow="wrap" %}
```
// Some code
```
{% endcode %}
In this case, a common problem is that multiple unused docker containers remain on the submission box. A simple solution is to prune unused containers:
```
docker system prune
```
or belows:
```
// Remove all stopped containers
% docker rm $(docker ps -a -q)
```
```
// or Remove all containers
% docker rm -f $(docker ps -a -q)
```
docker volume could not be changed even if the container was updated and relaunched
* Docker volume will not be changed and remained once it was created (except mount with -v). That is to say "exists independently".
* This is observed as well in using docker-compose. If you define and use volumes: in docker-compose.yml file, be cautious that the created volume will not be removed after invoking `docker compose down` .
* a workaround is to delete the docker volume beforehand
```
# Remove volumes
% docker volume rm
# or
% docker volume prune
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://iddynamics.gitbook.io/flepimop/how-to-run/common-errors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.