# Common errors

### Docker Issues

<details>

<summary>Docker Issues - storage full</summary>

* 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)
```

</details>

<details>

<summary>docker volume could not be changed even if the container was updated and relaunched</summary>

* 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 <specified volume name>
# or 
% docker volume prune
```

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://iddynamics.gitbook.io/flepimop/how-to-run/common-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.