Skip to content

Bind-mounted keystores in upgrades #3006

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 18, 2025
Merged

Bind-mounted keystores in upgrades #3006

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5926291
Bind-mounted keystores in upgrades
DaveCTurner Sep 18, 2025
7c45f3a
Update deploy-manage/deploy/self-managed/install-elasticsearch-docker…
DaveCTurner Sep 18, 2025
8fc87be
Merge branch 'main' into 2025/09/18/bind-mount-keystore-upgrade
DaveCTurner Sep 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions deploy-manage/deploy/self-managed/install-elasticsearch-docker-configure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,7 @@ If you’ve already created the keystore and don’t need to update it, you can
-e KEYSTORE_PASSWORD=mypassword
```

When you upgrade your cluster to a newer version, {{es}} will attempt to automatically upgrade the `elasticsearch.keystore` file to match. However, bind-mounted files are read-only, so {{es}} cannot automatically upgrade a bind-mounted `elasticsearch.keystore` file. Instead, if you are bind-mounting the `elasticsearch.keystore` file directly, you must use the `bin/elasticsearch-keystore upgrade` command to manually upgrade each node's keystore when you upgrade that node.

## Using custom Docker images [_c_customized_image]

Expand Down
Loading