9.2511.1

Default Elastic version: 9.2.0

Note
See version selection to run a different version.

Notable changes

• A new Compose service kibana-genkeys allows generating encryption keys for Kibana.

8.2511.1

Default Elastic version: 8.19.6

Note
See version selection to run a different version.

Notable changes

• A new Compose service kibana-genkeys allows generating encryption keys for Kibana.

9.2505.1

Default Elastic version: 9.0.1

Note
See version selection to run a different version.

Notable changes

• The main branch now follows the 9.x release series of Elastic components.

  Moving forward, all changes on the main branch should be considered incompatible with the 8.x release series, which is now being tracked on the release-8.x branch.

List of changes impacting docker-elk:

Kibana

• Several features now require an encryption key for saved objects. Such key must be set via the configuration option xpack.encryptedSavedObjects.encryptionKey.

  Ref: https://www.elastic.co/docs/deploy-manage/security/secure-saved-objects

Enterprise Search extension

• Discontinued in 9.x versions.

  Refs:

  • https://www.elastic.co/guide/en/enterprise-search/8.18/upgrading-to-9-x.html
  • https://www.elastic.co/blog/app-search-to-elasticsearch

8.2504.1

Default Elastic version: 8.17.4

Note
See version selection to run a different version.

Notable changes

• Metricbeat no longer fails to publish monitoring events due to the limit of total fields being exceeded when all default modules are enabled. This had already been fixed in the previous release, but eventually the limit got exceeded again after v8.16.0. The issue was addressed upstream in v8.16.2, making the limit configuration in docker-elk unnecessary.
• The Elastic Agent image is now docker.elastic.co/elastic-agent/elastic-agent instead of the (soon deprecated) docker.elastic.co/beats/elastic-agent image.

8.2410.1

Default Elastic version: 8.15.2

Note
See version selection to run a different version.

Notable changes

• The legacy docker-compose standalone (Compose v1) is no longer supported.
• Metricbeat no longer fails to publish monitoring events due to the limit of total fields being exceeded when all default modules are enabled.

8.2409.1

Default Elastic version: 8.15.1

Note
See version selection to run a different version.

Notable changes

• Docker no longer warns about missing default values for build arguments which could result in empty or invalid base image names. The associated build check is InvalidDefaultArgInFrom.

8.2402.1

Default Elastic version: 8.12.1

Note
See version selection to run a different version.

Notable changes

• The Fleet Server agent now has the Docker integration enabled by default, and collects the logs and metrics of all containers running on the host. This mirrors the default behaviour of the Metricsbeat and Filebeat extensions, making them obsolete for the aforementioned purpose.

8.2305.1

Default Elastic version: 8.7.1

Note
See version selection to run a different version.

Notable changes

• The setup container must now be run manually with docker-compose up setup. This makes the process of initializing users and groups more explicit, and allows re-initializing built-in users and groups with less effort. Please refer to #798 for more information.
• The minimum Compose version requirement was increased to 1.28.0.
• The curator extension was updated to v8.0. Curator is now major version locked with Elasticsearch. Please refer to the Curator Reference for more information.

8.2302.1

Default Elastic version: 8.6.2

Note
See version selection to run a different version.

Notable changes

• Elasticsearch, Logstash and Kibana now use the unless-stopped restart policy by default. As a result, their respective container gets restarted automatically after exiting, including after a reboot of the Docker host (but not when stopped manually with docker-compose [stop|down]).
• Fix Fleet Server extension listening on 127.0.0.1 (localhost) instead of 0.0.0.0 after upgrading to v8.6.

8.2212.1

Default Elastic version: 8.5.2

Note
See version selection to run a different version.

Notable changes

• Beats extensions no longer authenticate as the elastic superuser to send data to Elasticsearch. Instead, passwords for the filebeat_internal, metricbeat_internal and heartbeat_internal users (inactive by default) must be set respectively in the .env file.
• Monitoring of Elasticsearch, Logstash and Kibana is enabled by default via the Metricbeat extension. A password for the monitoring_internal user (inactive by default) must be set in the .env file for this to work.
• Self-monitoring is enabled by default in all Beats extensions. A password for the beat_system user (inactive by default) must be set in the .env file for this to work.
• Instructions for re-executing the setup were added. This allows resetting passwords to the values defined in the .env file, and forcing the creation of missing internal users and roles.
• It is no longer required to rebuild the image of the setup container when switching between the main and tls branches.