dependency failed to start: container magento-elasticsearch-1 is unhealthy

[Franz-Budon-Bapt]

Description Can't run the elasticsearch container Context : windows 10 wsl2 debian 12, existing project, had to do a bin/removeall to go for elasticsearch instead of opensearch

Steps To Reproduce

1. Follow the whole process (existing project procedure) and launch the command bin/start --no-dev I changed the configuration in both files compose.yaml and compose.healthcheck.yaml to use elasticsearch instead of opensearch (2 places in this one)

SOLUTIONS TESTED BUT NOT WORKING I trashed the debian and redo the whole process just to be sure the bin/removeall was not causing the issue. Still an error.

I tried to change environnement options in the configuration file, nothing works. environment:

• "discovery.type=single-node"

  Avoid test failures due to small disks

  More info at https://github.com/markshust/docker-magento/issues/488

• "cluster.routing.allocation.disk.threshold_enabled=false"
• "index.blocks.read_only_allow_delete"

  Uncomment to set custom heap size to avoid memory errors

  - "ES_JAVA_OPTS=-Xms1g -Xmx1g"

  Uncomment to increase the virtual memory map count

  - "max_map_count=262144"

Elasticsearch log file doesn't report of any memory issue.

I also tried with a different image version : markoshust/magento-elasticsearch:8.11.

Noted that some instructions in the documentation about switching between elasticsearch and opensearch are incorrect/outdated.

Expected Result magento-elasticsearch-1 healthy

Actual Result after 160s of booting up the magento-elasticsearch-1 container, it failed and we get the error message dependency failed to start: container magento-elasticsearch-1 is unhealthy

[YevhenZvieriev]

Hi, @Franz-Budon-Bapt

Adding this under environment of the elasticsearch image resolve your issue:

- "xpack.security.enabled=false"

[Franz-Budon-Bapt]

Hi, @Franz-Budon-Bapt

Adding this under environment of the elasticsearch image resolve your issue:

- "xpack.security.enabled=false"

It worked! Thanks a lot! How did you figure that one without me giving you any more details or logs ?

[YevhenZvieriev]

Glad to hear that.

A similar issue was resolved a few weeks ago, so people often face it.

I'll add a fix in the next PR as soon as possible.