Document update process for Docker deployments

[toby-sutor]

Add a section that describes on how to update Elasticsearch when running on Docker. Should probably be reviewed.

Source:

• https://discuss.elastic.co/t/how-to-upgrade-elasticsearch-in-docker-compose-yml/301408/2
• https://discuss.elastic.co/t/how-to-properly-upgrade-elasticsearch-running-as-docker-containers/221711/2
• https://discuss.elastic.co/t/upgrade-elk-on-docker-from-7-10-to-7-17/312839/6

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

@toby-sutor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

[elasticsearchmachine]

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

[leemthompo]

Just some formatting fixes, the numbered list one, for example, will fail docs build. :)

[leemthompo]

Suggested change

	==== Updating or Upgrading the Elasticsearch version running on Docker
	[discrete]
	[[docker-update-upgrade-elasticsearch-version]]
	==== Updating or upgrading the Elasticsearch version running on Docker

[leemthompo]

Suggested change

	1. Pull the new version of the Elasticsearch Docker image from Elastic's Docker registry using the `docker pull` command. Replace `x.y.z` with the version number you want to update to.
	----
	docker pull docker.elastic.co/elasticsearch/elasticsearch:x.y.z
	----
	2. Stop the currently running Elasticsearch container. Replace `container_name` with the name or ID of your Elasticsearch container.
	----
	docker stop container_name
	----
	3. Once the container has stopped, remove it. This will not delete your data if you have correctly mapped your data directory to a volume outside of the container.
	----
	docker rm container_name
	----
	4. Start a new container using the new image. Make sure to use the same volume mappings and configuration settings as the old container to ensure that your data and configuration are preserved. Replace `container_name` with the name you want for your new container.
	----
	docker run --name container_name -p 9200:9200 -p 9300:9300 \
	-e "discovery.type=single-node" \
	-v path_to_data_volume:/usr/share/elasticsearch/data \
	-v path_to_config_volume:/usr/share/elasticsearch/config \
	docker.elastic.co/elasticsearch/elasticsearch:x.y.z
	----
	Adjust the `-p` flags for port mappings, `-e` for environment variables, and `-v` for volume mappings as needed based on your setup.
	5. After the new container starts, verify that Elasticsearch is running the new version by querying the root URL of your Elasticsearch instance.
	. Pull the new version of the Elasticsearch Docker image from Elastic's Docker registry using the `docker pull` command. Replace `x.y.z` with the version number you want to update to.
	----
	docker pull docker.elastic.co/elasticsearch/elasticsearch:x.y.z
	----
	+
	. Stop the currently running Elasticsearch container. Replace `container_name` with the name or ID of your Elasticsearch container.
	----
	docker stop container_name
	----
	+
	. Once the container has stopped, remove it. This will not delete your data if you have correctly mapped your data directory to a volume outside of the container.
	----
	docker rm container_name
	----
	+
	. Start a new container using the new image. Make sure to use the same volume mappings and configuration settings as the old container to ensure that your data and configuration are preserved. Replace `container_name` with the name you want for your new container.
	----
	docker run --name container_name -p 9200:9200 -p 9300:9300 \
	-e "discovery.type=single-node" \
	-v path_to_data_volume:/usr/share/elasticsearch/data \
	-v path_to_config_volume:/usr/share/elasticsearch/config \
	docker.elastic.co/elasticsearch/elasticsearch:x.y.z
	----
	+
	Adjust the `-p` flags for port mappings, `-e` for environment variables, and `-v` for volume mappings as needed based on your setup.
	+
	. After the new container starts, verify that Elasticsearch is running the new version by querying the root URL of your Elasticsearch instance.

[leemthompo]

list will still be numbered FYI just need the +s to keep items connected

[leemthompo]

Suggested change

	- Always back up your data before performing an update, especially for production environments.
	- Review the Elasticsearch release notes for the new version to be aware of any breaking changes or required actions before or after the update.
	- If you're using custom plugins or configurations, ensure they are compatible with the new version and reapply them if necessary.
	- If you're running a cluster, you'll need to carefully plan the upgrade process to minimize downtime and ensure cluster stability. This often involves a rolling upgrade strategy.
	- When using a `docker-compose.yml` make sure to update the desired version in the configuration file or the environment variable.
	* Always back up your data before performing an update, especially for production environments.
	* Review the Elasticsearch release notes for the new version to be aware of any breaking changes or required actions before or after the update.
	* If you're using custom plugins or configurations, ensure they are compatible with the new version and reapply them if necessary.
	* If you're running a cluster, you'll need to carefully plan the upgrade process to minimize downtime and ensure cluster stability. This often involves a rolling upgrade strategy.
	* When using a `docker-compose.yml` make sure to update the desired version in the configuration file or the environment variable.

[leemthompo]

Important

Elastic documentation is migrating to Markdown for version 9.0+. See the migration guide for details.

ℹ️ What's happening?

• Starting January 29, we will start closing all unmerged documentation PRs targeting main/master
• We're migrating from AsciiDoc to Markdown for 9.0+
• 9.0 docs will be frozen from January 29 until February 20 2024
• NOTE: PRs that include both code and documentation changes will remain open

What do I need to do?

For <=8.x docs:

1. Rebase your PR to target the relevant 8.x branch instead
2. The content can remain in AsciiDoc format

For 9.0+ docs:

Option 1:

• Draft docs in Markdown
• Once migration freeze ends, find the relevant page in the new docs system and use the edit options to submit your changes

Option 2:

• Open an issue in elastic/docs-content

💡 Need help?

1. For Elasticians: Ask in #docs Slack channel
2. For external contributors: Open an issue in elastic/docs-content

[leemthompo]

@toby-sutor any reason why this wasn't pursued? :)