Elasticsearch docker-entrypoint.sh script overwrite

NK2812 · December 22, 2020, 6:07pm

Hi,

I need to run few commands when container starts, so I would like add those commands in docker-entrypoint.sh script.

I am using Elasticsearch version 7.9.2, I tried to create the cluster without adding my custom commands in the docker-entrypoint.sh script but it is failing and if I don't specify the entry point it is creating cluster. I need to mention entrypoint as I would need to run few commands.

Here is my docker file,

FROM docker.elastic.co/elasticsearch/elasticsearch:7.9.2

ENTRYPOINT ["/usr/local/bin/docker-entrypoint.sh"]

CMD ["eswrapper"]

Error message
java.lang.RuntimeException: can not run elasticsearch as root
at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:111)
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:178)
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:393)
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170)
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161)
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86)
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127)
at org.elasticsearch.cli.Command.main(Command.java:90)
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126)

Copied the docker-entrypoint.sh content from here

github.com

elastic/elasticsearch/blob/master/distribution/docker/src/docker/bin/docker-entrypoint.sh

#!/bin/bash
set -e

# Files created by Elasticsearch should always be group writable too
umask 0002

# Allow user specify custom CMD, maybe bin/elasticsearch itself
# for example to directly specify `-E` style parameters for elasticsearch on k8s
# or simply to run /bin/bash to check the image
if [[ "$1" == "eswrapper" || $(basename "$1") == "elasticsearch" ]]; then
  # Rewrite CMD args to remove the explicit command,
  # so that we are backwards compatible with the docs
  # from the previous Elasticsearch versions < 6
  # and configuration option:
  # https://www.elastic.co/guide/en/elasticsearch/reference/5.6/docker.html#_d_override_the_image_8217_s_default_ulink_url_https_docs_docker_com_engine_reference_run_cmd_default_command_or_options_cmd_ulink
  # Without this, user could specify `elasticsearch -E x.y=z` but
  # `bin/elasticsearch -E x.y=z` would not work. In any case,
  # we want to continue through this script, and not exec early.
  set -- "${@:2}"
else

This file has been truncated. show original

Please help me out why it is failing

system · January 19, 2021, 6:07pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Creating and loading index after Elasticsearch docker container bootstrap Elasticsearch docker	2	2475	June 15, 2020
Installing plugins on elasticsearch docker image using custom Dockerfile Elasticsearch	1	3827	January 6, 2018
Elasticsearch Keystore not being created Elasticsearch docker	12	1875	September 17, 2023
Want to use Elasticsearch as a base image Elasticsearch	8	526	May 18, 2023
Running the script in elasticsearch docker-compose Elasticsearch	2	727	March 31, 2021

Elasticsearch docker-entrypoint.sh script overwrite

Related topics