Adds known issue for aarch64 pwd generation

[jkakavas]

We figured out that on Linux and macOS aarch64, we can't
determine whether a terminal is attached to elasticsearch and as
such we don't print the elastic password and enrollment token on
node first startup. This is resolved in #83566 by updating the
underlying library we use to detect the terminal.

[elasticmachine]

Pinging @elastic/es-docs (Team:Docs)

[lockewritesdocs]

Added a suggested reworking of this note. It's a little more verbose with the examples, but I think that they stand out better and are easier to read.

[tvernum]

Do we think readers understand aarch64? Do we need to explicitly say "ARM" or "M1"?

[jkakavas]

Good point, I used Linux aarch64 and macOS aarch64 because that's what the download option says in the download page but we can definitely change this to "Linux ARM or macOS M1"

[leemthompo]

@tvernum @lockewritesdocs Hail fellow Elasticians 👋

I ran into this issue when reviewing the updated 8.0 Docker instructions for the Enterprise Search docs. This requires using docker run in interactive mode with the -it flag. Because the password/enrollment tokens are not generated within the running ES process in the container, I haven't found a workaround for this. If there isn't a workaround, users should be warned!

Because you don't have access to an interactive TTY within the container, you can't run the bin/elasticsearch-reset-password tool. Is that correct?

[jkakavas]

Hi there @leemthompo.

This is slightly different, as this is not a "known issue". Not generating the password and the enrollment token when there is no terminal attached is a conscious design decision we made as we want to limit the exposure of these in logs and well, when there is no terminal attached, there is noone to see the output :).

Our docs for running elasticsearch with docker on 8.0 specify the -it parameter so by default users will run with a terminal attached.
Even if you don't run the container in interactive mode, you can always use docker exec to run the CLI utility in the container, we document that too in that page :

docker exec -it es01 /usr/share/elasticsearch/bin/elasticsearch-reset-password

[leemthompo]

@jkakavas Thanks for that info! I guess the problem then is that running with the -it flag on Mac M1 the container "cannot determine if there is a terminal attached to the elasticsearch process". But good to know that there is a workaround. Cheers.

[jkakavas]

@jkakavas Thanks for that info! I guess the problem then is that running with the -it flag on Mac M1 the container "cannot determine if there is a terminal attached to the elasticsearch process". But good to know that there is a workaround. Cheers.

Correct, the Mac M1 specific thing is the known issue here, and we have fixed that in 8.0.1 and 8.1.0

[jrodewig]

Wanted to note that this will also be in the 8.0.0 GA release notes with #83689.

Please ensure any changes here get synced with the 8.0.0 GA release notes. Thanks!

[jkakavas]

I'm merging this as a I have accepted @lockewritesdocs and @tvernum suggestions

[st11x]

@jkakavas Thanks for that info! I guess the problem then is that running with the -it flag on Mac M1 the container "cannot determine if there is a terminal attached to the elasticsearch process". But good to know that there is a workaround. Cheers.

Correct, the Mac M1 specific thing is the known issue here, and we have fixed that in 8.0.1 and 8.1.0

I just pulled the 8.1.0 image and ran it in develop mode as described at https://hub.docker.com/_/elasticsearch. I am also getting this problem with Ubuntu 20.04 x86_64.

[tvernum]

Hi @st11x

Your problem is almost certainly different. This was a very specific issue that terminal recognition didn't work correctly on ARM. That problem has been solved, and whatever issue you're seeing will be different.

Can you please either:

1. Open a new issue and clearly describe the behaviour you're seeing (error messages, log files) and your environment (ES version, OS, packaging method, init method).
2. Start a discussion on our forums where we can talk through what you're seeing and try and diagnose the cause.

[st11x]

Okay, I will do that. Thanks.