bump compose files to elasticsearch 8 (see #9)

ccs-amsterdam · Jun 20, 2023 · 57bfcae · 57bfcae
1 parent 7eb2233
commit 57bfcae
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 8 deletions.
diff --git a/docker-compose-feature.yml b/docker-compose-feature.yml
@@ -47,7 +47,7 @@ services:
     depends_on:
       - "db"
   db:
-    image: docker.elastic.co/elasticsearch/elasticsearch:7.17.9
+    image: docker.elastic.co/elasticsearch/elasticsearch:8.8.1
     container_name: elastic7
     restart: unless-stopped
     # for security reasons, the database is only exposed to the other containers in the amcat-net network
@@ -63,7 +63,7 @@ services:
       - "ES_JAVA_OPTS=-Xms4g -Xmx4g"
       - xpack.security.enabled=false
     # your database should have a folder on the host machine to permanently store data. By default
-    # a docker volume is used, which leaves management of the files to Docker 
+    # a docker volume (called elastic-volume) is used, which leaves management of the files to Docker 
     # (see https://docs.docker.com/storage/volumes/). You can also store files somewhere else with
     # (for example):
     #

diff --git a/docker-compose-https.yml b/docker-compose-https.yml
@@ -46,7 +46,7 @@ services:
     depends_on:
       - "db"
   db:
-    image: docker.elastic.co/elasticsearch/elasticsearch:7.17.9
+    image: docker.elastic.co/elasticsearch/elasticsearch:8.8.1
     container_name: elastic7
     restart: unless-stopped
     # for security reasons, the database is only exposed to the other containers in the amcat-net network
@@ -62,7 +62,7 @@ services:
       - "ES_JAVA_OPTS=-Xms4g -Xmx4g"
       - xpack.security.enabled=false
     # your database should have a folder on the host machine to permanently store data. By default
-    # a docker volume is used, which leaves management of the files to Docker 
+    # a docker volume (called elastic-volume) is used, which leaves management of the files to Docker 
     # (see https://docs.docker.com/storage/volumes/). You can also store files somewhere else with
     # (for example):
     #

diff --git a/docker-compose-nightlies.yml b/docker-compose-nightlies.yml
@@ -41,7 +41,7 @@ services:
     depends_on:
       - "db"
   db:
-    image: docker.elastic.co/elasticsearch/elasticsearch:7.17.9
+    image: docker.elastic.co/elasticsearch/elasticsearch:8.8.1
     container_name: elastic7
     restart: unless-stopped
     # for security reasons, the database is only exposed to the other containers in the amcat-net network
@@ -57,7 +57,7 @@ services:
       - "ES_JAVA_OPTS=-Xms4g -Xmx4g"
       - xpack.security.enabled=false
     # your database should have a folder on the host machine to permanently store data. By default
-    # a docker volume is used, which leaves management of the files to Docker 
+    # a docker volume (called elastic-volume) is used, which leaves management of the files to Docker 
     # (see https://docs.docker.com/storage/volumes/). You can also store files somewhere else with
     # (for example):
     #

diff --git a/docker-compose.yml b/docker-compose.yml
@@ -41,7 +41,7 @@ services:
     depends_on:
       - "db"
   db:
-    image: docker.elastic.co/elasticsearch/elasticsearch:7.17.9
+    image: docker.elastic.co/elasticsearch/elasticsearch:8.8.1
     container_name: elastic7
     restart: unless-stopped
     # for security reasons, the database is only exposed to the other containers in the amcat-net network
@@ -57,7 +57,7 @@ services:
       - "ES_JAVA_OPTS=-Xms4g -Xmx4g" 
       - xpack.security.enabled=false
     # your database should have a folder on the host machine to permanently store data. By default
-    # a docker volume is used, which leaves management of the files to Docker 
+    # a docker volume (called elastic-volume) is used, which leaves management of the files to Docker 
     # (see https://docs.docker.com/storage/volumes/). You can also store files somewhere else with
     # (for example):
     #