docker-entrypoint.sh uses a mix of absolute and relative/implied paths #98643
Labels
>bug
:Delivery/Packaging
RPM and deb packaging, tar and zip archives, shell and batch scripts
Team:Delivery
Meta label for Delivery team
We invoke
elasticsearch
via its absolute path here:elasticsearch/distribution/docker/src/docker/bin/docker-entrypoint.sh
Line 84 in d5b1356
However we also invoke
elasticsearch-keystore
in several places, and none of them specify its path so we are relying on picking up the right binary from$PATH
. For instance:elasticsearch/distribution/docker/src/docker/bin/docker-entrypoint.sh
Line 43 in d5b1356
We also check for the existence of
bin/elasticsearch-users
relative to the current directory:elasticsearch/distribution/docker/src/docker/bin/docker-entrypoint.sh
Line 35 in d5b1356
Should these all be absolute paths to avoid any ambiguity if running in a slightly weird environment? I ask because a user on the forums needed to make some adjustments to how we start up within their Docker environment, and these non-absolute paths got in their way a bit.
The text was updated successfully, but these errors were encountered: