magento-opensearch-1 container fails to start during one-liner setup on WSL

[jagustin08]

Description

I'm trying to set up a Magento 2.4.8 project using the one-liner setup script from this repo. The setup fails due to the magento-opensearch-1 container crashing immediately.

Steps to Reproduce

1. On WSL (Ubuntu), run:

   mkdir -p ~/Sites/magento
   cd $_
   curl -s https://raw.githubusercontent.com/markshust/docker-magento/master/lib/onelinesetup | bash -s -- magento.test community 2.4.8
   

2. Observe that the setup fails during the OpenSearch container startup.

Actual Result

• All other containers start and become healthy.
• magento-opensearch-1 exits with status 1.
• Output includes:

✘ Container magento-opensearch-1 Error
dependency failed to start: container magento-opensearch-1 exited (1)

[dosubot]

Hello @jagustin08! I'm Dosu, your friendly bot here to help you tackle bugs, answer questions, and assist you in becoming a contributor. I'm ready to help while you wait for a human maintainer. Let's get started!

To resolve the magento-opensearch-1 container startup failure during the one-liner setup of a Magento 2.4.8 project on WSL, you can try the following approaches:

1. Comment out or remove the _JAVA_OPTIONS: -XX:UseSVE=0 line in the env/opensearch.env file. This Java option is intended for ARM64/Apple M-series chips and can cause compatibility issues on non-ARM architectures like Intel processors ^[1].

2. Alternatively, replace the OpenSearch section in the compose.yaml file with the following Elasticsearch configuration to switch from OpenSearch to Elasticsearch, which might resolve the startup issues:

   elasticsearch:
     image: docker.elastic.co/elasticsearch/elasticsearch:7.16.3
     container_name: magento-elasticsearch
     environment:
       - discovery.type=single-node
       - xpack.security.enabled=false
       - bootstrap.memory_lock=true
     ulimits:
       memlock:
         soft: -1
         hard: -1
     mem_limit: 2g
     ports:
       - "9200:9200"

This solution has been effective for similar issues ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[Maximize1107]

I am having this same issue as well.

`✘ Container magento-opensearch-1 Error 1.0s
dependency failed to start: container magento-opensearch-1 exited (1)

chris@ubuntu:~/Sites/magento$ docker logs magento-opensearch-1
Disabling OpenSearch Security Plugin
Enabling execution of OPENSEARCH_HOME/bin/opensearch-performance-analyzer/performance-analyzer-agent-cli for OpenSearch Performance Analyzer Plugin
Picked up _JAVA_OPTIONS: -XX:UseSVE=0
Unrecognized VM option 'UseSVE=0'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Disabling OpenSearch Security Plugin
Enabling execution of OPENSEARCH_HOME/bin/opensearch-performance-analyzer/performance-analyzer-agent-cli for OpenSearch Performance Analyzer Plugin
Picked up _JAVA_OPTIONS: -XX:UseSVE=0
Unrecognized VM option 'UseSVE=0'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

chris@ubuntu:~/Sites/magento$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.2 LTS
Release: 24.04
Codename: noble

chris@ubuntu:/Sites/magento$ docker --version
Docker version 26.1.3, build 26.1.3-0ubuntu124.04.1
`

[Maximize1107]

Ok I have ran:

nano ./env/opensearch.env
nano ./env/elasticsearch.env

and then I commented out:

_JAVA_OPTIONS: -XX:UseSVE=

What do I do after this?

[markshust]

Sorry, I'm unable to replicate this, but will keep it open so the community can resolve this. I'd gladly take in a PR to resolve it.

[markshust]

Possibly related? #1333

[markshust]

This appears to be a dupe of #1333 so I'm closing this out. I just issued a hotfix which should resolve this issue.