From bb84bf6c154e3bdbce70cea4622362843c9e1edb Mon Sep 17 00:00:00 2001 From: "opensearch-trigger-bot[bot]" <98922864+opensearch-trigger-bot[bot]@users.noreply.github.com> Date: Mon, 14 Nov 2022 09:07:35 -0800 Subject: [PATCH] Fixed Docker command with custom file path (#1860) (#1861) Signed-off-by: JeffH-AWS Signed-off-by: JeffH-AWS (cherry picked from commit f7ba853a85cd5599fac8b42275fa21016da152b5) Co-authored-by: Jeff Huss --- _opensearch/install/docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_opensearch/install/docker.md b/_opensearch/install/docker.md index f232345dcb..d2623396d5 100644 --- a/_opensearch/install/docker.md +++ b/_opensearch/install/docker.md @@ -129,7 +129,7 @@ If none of those files exist in your current directory, the `docker-compose` com You can specify a custom file location and name when invoking `docker-compose` with the `-f` flag: ```bash # Use a relative or absolute path to the file. -docker-compose up -f /path/to/your-file.yml +docker-compose -f /path/to/your-file.yml up ``` If this is your first time launching an OpenSearch cluster using Docker Compose, use the following example `docker-compose.yml` file. Save it in the home directory of your host and name it `docker-compose.yml`. This file will create a cluster that contains three containers: two containers running the OpenSearch service and a single container running OpenSearch Dashboards. These containers will communicate over a bridge network called `opensearch-net` and use two volumes, one for each OpenSearch node. Because this file does not explicitly disable the demo security configuration, self-signed TLS certificates are installed and internal users with default names and passwords are created.