Issue with Docker stack deployment

[swaybs]

I have run through the correct steps in the documentation to deploy the stack via docker-compose. I have changed the default values for .env file and generated new UUID's. When the stack deploys, and I try to connect to port 8080, I get a refused to connect on that port.

Logs for opencti container: ERR [OPENCTI] System dependencies check failed | category=APP dependencyError={"_error":{},"_showLocations":false,"_showPath":false,"data":{"cause":{"meta":{"body":null,"headers":null,"meta":{"aborted":false,"attempts":3,"connection":{"_openRequests":0,"deadCount":4,"headers":{},"id":"http://elasticsearch:9200/","resurrectTimeout":1714566800942,"roles":{"data":true,"ingest":true},"status":"dead","url":"http://elasticsearch:9200/"},"context":null,"name":"opensearch-js","request":{"id":1,"options":{},"params":{"body":null,"headers":{"user-agent":"opensearch-js/2.6.0 (linux 5.15.0-105-generic-x64; Node.js v20.12.0)"},"method":"GET","path":"/","querystring":"","timeout":30000}}},"statusCode":null},"name":"ConnectionError"},"genre":"TECHNICAL","http_status":500},"internalData":{},"name":"CONFIGURATION_ERROR","time_thrown":"2024-05-01T12:25:20.943Z"} timestamp=2024-05-01T12:25:20.943Z version=6.0.9

ERR Search engine seems down | category=APP errors=[{"attributes":{"genre":"TECHNICAL","http_status":500},"message":"Search engine seems down","name":"CONFIGURATION_ERROR","stack":"CONFIGURATION_ERROR: Search engine seems down\n at error (/opt/opencti/build/src/config/errors.js:8:10)\n at ConfigurationError (/opt/opencti/build/src/config/errors.js:70:53)\n at /opt/opencti/build/src/database/engine.js:235:15\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at searchEngineVersion (/opt/opencti/build/src/database/engine.js:231:22)\n at searchEngineInit (/opt/opencti/build/src/database/engine.js:279:27)\n at checkSystemDependencies (/opt/opencti/build/src/initialization.js:31:3)\n at platformStart (/opt/opencti/build/src/boot.js:14:7)"},{"message":"getaddrinfo EAI_AGAIN elasticsearch","name":"ConnectionError","stack":"ConnectionError: getaddrinfo EAI_AGAIN elasticsearch\n at ClientRequest.onError (/opt/opencti/build/node_modules/@opensearch-project/opensearch/lib/Connection.js:129:16)\n at ClientRequest.emit (node:events:518:28)\n at Socket.socketErrorListener (node:_http_client:500:9)\n at Socket.emit (node:events:518:28)\n at emitErrorNT (node:internal/streams/destroy:169:8)\n at emitErrorCloseNT (node:internal/streams/destroy:128:3)\n at processTicksAndRejections (node:internal/process/task_queues:82:21)"}] timestamp=2024-05-01T12:25:20.947Z version=6.0.9

Logs for opencit-elasticsearch container: Exception in thread "main" java.lang.RuntimeException: starting java failed with [1] output: There is insufficient memory for the Java Runtime Environment to continue. Native memory allocation (mmap) failed to map 8589934592 bytes. Error detail: committing reserved memory. An error report file with more information is saved as: logs/hs_err_pid28.log error: OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000600000000, 8589934592, 0) failed; error='Not enough space' (errno=12) at org.elasticsearch.server.cli.JvmOption.flagsFinal(JvmOption.java:120) at org.elasticsearch.server.cli.JvmOption.findFinalOptions(JvmOption.java:87) at org.elasticsearch.server.cli.MachineDependentHeap.determineHeapSettings(MachineDependentHeap.java:59) at org.elasticsearch.server.cli.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:141) at org.elasticsearch.server.cli.JvmOptionsParser.determineJvmOptions(JvmOptionsParser.java:92) at org.elasticsearch.server.cli.ServerCli.startServer(ServerCli.java:248) at org.elasticsearch.server.cli.ServerCli.execute(ServerCli.java:100) at org.elasticsearch.common.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:54) at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:85) at org.elasticsearch.cli.Command.main(Command.java:50) at org.elasticsearch.launcher.CliToolLauncher.main(CliToolLauncher.java:64)