[BUG] DEV docker compose file is not running correctly #464
Comments
|
Below can be ignored, turns out the docker fails when setting the working_dir. After removing it from my yaml, the docker did start. Might be something to look into . I've tried both YML's without success, they keep giving: ERROR: for opensearch13 Cannot start service opensearch13: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "./opensearch-docker-entrypoint.sh": stat ./opensearch-docker-entrypoint.sh: no such file or directory: unknown ERROR: for opensearch12 Cannot start service opensearch12: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "./opensearch-docker-entrypoint.sh": stat ./opensearch-docker-entrypoint.sh: no such file or directory: unknown ERROR: for opensearch13 Cannot start service opensearch13: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "./opensearch-docker-entrypoint.sh": stat ./opensearch-docker-entrypoint.sh: no such file or directory: unknown I use this YAML: version: "3.7"
services:
opensearch12:
container_name: opensearch12
image: opensearchproject/opensearch:1.2.4
restart: always
networks:
- xsa_backend
ports:
- "9312:9200" # 93xx used to avoid conflicts with Elastic Search
- "9612:9600" # required for Performance Analyzer
working_dir: /sites
environment:
- cluster.name=opensearch12-cluster
- node.name=opensearch12
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- "OPENSEARCH_JAVA_OPTS=-Xms1g -Xmx1g" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
- "DISABLE_INSTALL_DEMO_CONFIG=true" # disables execution of install_demo_configuration.sh bundled with security plugin, which installs demo certificates and security configurations to OpenSearch
- "DISABLE_SECURITY_PLUGIN=true" # disables security plugin entirely in OpenSearch by setting plugins.security.disabled: true in opensearch.yml
- "discovery.type=single-node" # disables bootstrap checks that are enabled when network.host is set to a non-loopback address
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
opensearch12-dashboards:
container_name: opensearch12-dashboards
image: opensearchproject/opensearch-dashboards:1.2.0
restart: always
networks:
- xsa_backend
ports:
- 5612:5601
expose:
- "5601"
environment:
- 'OPENSEARCH_HOSTS=["http://opensearch12:9200"]'
- "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" # disables security dashboards plugin in OpenSearch Dashboardsversion: "3.7"
services:
opensearch13:
container_name: opensearch13
image: opensearchproject/opensearch:1.3.0
restart: always
networks:
- xsa_backend
ports:
- "9313:9200" # 93xx used to avoid conflicts with Elastic Search
- "9613:9600" # required for Performance Analyzer
working_dir: /sites
environment:
- cluster.name=opensearch13-cluster
- node.name=opensearch13
- bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
- "OPENSEARCH_JAVA_OPTS=-Xms1g -Xmx1g" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
- "DISABLE_INSTALL_DEMO_CONFIG=true" # disables execution of install_demo_configuration.sh bundled with security plugin, which installs demo certificates and security configurations to OpenSearch
- "DISABLE_SECURITY_PLUGIN=true" # disables security plugin entirely in OpenSearch by setting plugins.security.disabled: true in opensearch.yml
- "discovery.type=single-node" # disables bootstrap checks that are enabled when network.host is set to a non-loopback address
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
hard: 65536
opensearch13-dashboards:
container_name: opensearch13-dashboards
image: opensearchproject/opensearch-dashboards:1.3.0
restart: always
networks:
- xsa_backend
ports:
- 5613:5601
expose:
- "5613"
environment:
- 'OPENSEARCH_HOSTS=["http://opensearch13:9200"]'
- "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true" # disables security dashboards plugin in OpenSearch DashboardsI'v tried it too while
|
|
@peterzhuamazon i get the same error when trying a simple copy/paste/compose of the dev example. i was able to get the dev example running by rolling the container tags back to this adds a lot of friction for anyone wanting to try out opensearch, especially since that example is where i landed from searching. it wasn't clear to me how to fix this error from the docs, since searching the cluster formation doc page indicates:
a link to the minor, but clearly important, adjustments would be helpful there. |
|
@johns1342 the yaml's from my previous comment work when you remove 'working_dir'. |
|
hi @evs-xsarus, i don't see a working_dir in the v2 docker compose example @peterzhuamazon linked to. fwiw your example config is using v1 images as well, which does work for me with the example config. it appears 2.0.1 fixed this issue for me. the only difference in the example is it's pulling 2.0.1 image instead of 2.0.0 image. |
JeffHuss
added
1 - Backlog
|
I'm taking a look at this. Starting with testing versions from
*Sample file for developers was not present so I only tested with the sample |
|
Based on my findings, this was already fixed. I specifically tested against versions 2.0.1 and 2.0.0 since I saw John called that out, but they both downloaded and launched without issue. I was able to open a terminal session with each version. Closing this issue out. If you feel I've overlooked something please let me know. |
JeffHuss
added
Closed - Won't fix
and removed
bug
Coming from here:
https://opensearch.org/docs/latest/opensearch/install/docker/#sample-docker-compose-file-for-development
This docker file trying to do single node deployment of OS and OSD but have errors after startup:
Not completely the same error but seems like it hasnt run for a while:
opensearch-project/opensearch-build#1775 (comment)
@Naarcha-AWS if you can take a look would be great.
Thanks.
The text was updated successfully, but these errors were encountered: