Is the Docker implementation flawed in Unraid? Unable to use Elasticsearch 8.15 (works with Docker Desktop)

[Motsols]

I have followed this official guide https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html

 

It is simple enough, run this to download and create the container

docker run --name es01 -p 9200:9200 -it -m 1GB docker.elastic.co/elasticsearch/elasticsearch:8.15.0

 

That fails with some error messages which is already different from how it should be. With some fiddling around, this starts a server at least:

docker run --name es01 -e "xpack.security.enabled=true" -e "xpack.security.enrollment.enabled=true" -e "discovery.type=single-node" --net elastic -p 9200:9200 -it -m 2GB docker.elastic.co/elasticsearch/elasticsearch:8.15.0

 

The server starts but with the following issues in the console, so it's not possible to enroll Kibana:

❌ Unable to generate an enrollment token for Kibana instances, try invoking `bin/elasticsearch-create-enrollment-token -s kibana`.

❌ An enrollment token to enroll new nodes wasn't generated. To add nodes and enroll them into this cluster:
• On this node:
  ⁃ Create an enrollment token with `bin/elasticsearch-create-enrollment-token -s node`.
  ⁃ Restart Elasticsearch.
• On other nodes:
  ⁃ Start Elasticsearch with `bin/elasticsearch --enrollment-token <token>`, using the enrollment token that you generated.

 

To connect Kibana to the Elasticsearch server I need to create an enrollment token using this command

docker exec -it es01 /usr/share/elasticsearch/bin/elasticsearch-create-enrollment-token -s kibana

 

This last command fails with the error

Unable to create enrollment token for scope [kibana]

ERROR: Unable to create an enrollment token. Elasticsearch node HTTP layer SSL configuration is not configured with a keystore, with exit code 73

This last command also works perfectly fine with Docker Desktop but not on unraid, which leaves me to believe that something is different with the Unraid implementation.

 

I can't believe Elasticsearch wouldn't be able to run on Unraid, but so far the commands obviously don't work even though I can run them on Windows with Docker Desktop.

 

Is there a bug or an issue in the Unraid implementation of Docker?

[primeval_god]

39 minutes ago, Motsols said:

Is there a bug or an issue in the Unraid implementation of Docker?

Unlikely to be anything specific to the unRAID OS. Its possible that it is meant for a different version of the docker engine than unRAID has installed.  What version of unRAID are your running (and more to the point what version of the Docker engine does it contain). What version of the docker engine do you have in Docker desktop? 

[Motsols]

Good input.

 

I am running the latest Unraid, version 6.12.11 which has Docker version 24.0.9.

My Docker Desktop on Windows has Docker version 27.1.1.

 

After glancing at the last few versions I don't see something that means Elasticsearch would stop working as it seems like unrelated changes https://docs.docker.com/engine/release-notes/27.0/

 

Edit:

Elasticsearch v8 which started with this enrollment launched in february last year.

Docker desktop got docker engine version 24.0.7 only in december last year, so it should definitely have been working already by that version.

Edited August 9 by Motsols

[Kilrah]

Their instructions say to create a network and connect both to this network, it's probably required for them to discover each other. When you run a compose stack one is made by default for the stack if none is supplied, if you run them separately it's your job to do it. 

[Motsols]

The network was created already before this, but didn't mention it since it's not relevant.

I didn't write it since the container does start, but can't create an enrollment token. SInce it only happens on Unraid I suspect an issue with Unraid.

[Kilrah]

Try to do it in compose with the compose manager plugin

[Motsols]

Correct me if I'm wrong, but why would docker compose manager help here if I'm not using docker compose?

Does the app itself have an option to start individual docker containers as well without compose? Not from what I saw on the app info.

[Kilrah]

33 minutes ago, Motsols said:

Correct me if I'm wrong, but why would docker compose manager help here if I'm not using docker compose?

Because I'm suggesting you try doing it in compose instead

Edited August 10 by Kilrah

[whipdancer]

23 hours ago, Motsols said:

Good input.

 

I am running the latest Unraid, version 6.12.11 which has Docker version 24.0.9.

My Docker Desktop on Windows has Docker version 27.1.1.

 

After glancing at the last few versions I don't see something that means Elasticsearch would stop working as it seems like unrelated changes https://docs.docker.com/engine/release-notes/27.0/

 

Edit:

Elasticsearch v8 which started with this enrollment launched in february last year.

Docker desktop got docker engine version 24.0.7 only in december last year, so it should definitely have been working already by that version.

Try downgrading your version of docker desktop to 24.x and compare.