# Compose down

`POST /compose/down`

Stop and remove a compose project

**Example request**:

```
POST /compose/down?project=blog HTTP/1.1
```

**Example response**:

```
HTTP/1.1 201 OK

Content-Type: application/json

{"status":"Project [blog]: Stopping project "}
{"status":"[0/2] [web]: Stopping "}
{"status":"[0/2] [db]: Stopping "}
{"status":"[0/2] [web]: Stopped "}
{"status":"[0/2] [db]: Stopped "}
{"status":"Project [blog]: Project stopped "}
{"status":"Project [blog]: Deleting project "}
{"status":"[0/2] [web]: Deleting "}
{"status":"[0/2] [db]: Deleting "}
{"status":"[0/2] [web]: Deleted "}
{"status":"[0/2] [db]: Deleted "}
{"status":"Project [blog]: Project deleted "}
```

Status Codes:

* **201** - no error
* **500** - Internal Server Error

Parameters:

* **project** - The name of compose project.
* **services** - The services to operate, many services will be splited by '}{'.
* **rmorphans** - Remove containers for services not defined in the Compose file.
* **rmi** - Remove images, type may be one of: 'all' to remove all images, or 'local' to remove only images that don't have an custom name set by the `image` field.
* **vol** - Remove data volumes.


---

# 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://hyperhq.gitbook.io/docs-hyper-sh/index-2/index-1/index/index-9/compose_down.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.