> For the complete documentation index, see [llms.txt](https://docs.omnileads.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnileads.net/english/omnileads-installation-methods/deploy-using-docker.md).

# Deploy using Docker

It is required to have Docker-Engine installed in the deployment environment (Linux, Mac, or Windows). \
\
In the following section, we will cover the steps necessary to have OMniLeads running in dockerized environments.

* [Docker Install documentation](https://docs.docker.com/get-docker/)

and the following cloned repository:

```
git clone https://gitlab.com/omnileads/omldeploytool.git
cd omldeploytool/docker-compose
```

## OMniLeads & Docker Compose <a href="#user-content-omnileads-docker-compose" id="user-content-omnileads-docker-compose"></a>

In the directory, we will find 3 Docker Compose files:

**1) docker-compose.yml**: It is used to launch the stack of containers on the workstation where Docker Desktop resides.

**2) docker-compose\_prod.yml**: used to launch the stack on a Cloud VPS (Virtual Private Server) or VM (Virtual Machine).

**3) docker-compose\_prod\_external\_bucket.yml**: Similar to the previous scenario, but including an external bucket (Object Storage - S3).

To create a .env file, copy the example env file provided in the repository:

```
$ cp env .env 
```

According to the chosen scenario, we will follow the steps described in each section:

* [Docker Desktop](/english/omnileads-installation-methods/deploy-using-docker/deploy-with-docker-destkop.md)
* [Docker en VPS Cloud o VM](/english/omnileads-installation-methods/deploy-using-docker/deploy-with-docker-for-vps-cloud-or-vm.md)
* [Docker en VPS Cloud o VM utilizando Bucket Externo](/english/omnileads-installation-methods/deploy-using-docker/deploy-with-docker-for-vps-cloud-or-vm-with-external-bucket.md)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.omnileads.net/english/omnileads-installation-methods/deploy-using-docker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.