fix: Disable generated warning in docker compose (#8916)

risingwavelabs · Mar 31, 2023 · 188846e · 188846e
1 parent 85ecc73
commit 188846e
Showing 1 changed file with 5 additions and 6 deletions.
diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml
@@ -29,7 +29,7 @@ services:
     environment:
       RUST_BACKTRACE: "1"
       # If ENABLE_TELEMETRY is not set, telemetry will start by default
-      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY}
+      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY:-true}
     container_name: compactor-0
     healthcheck:
       test:
@@ -70,7 +70,7 @@ services:
     environment:
       RUST_BACKTRACE: "1"
       # If ENABLE_TELEMETRY is not set, telemetry will start by default
-      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY}
+      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY:-true}
     container_name: compute-node-0
     healthcheck:
       test:
@@ -82,8 +82,7 @@ services:
       timeout: 5s
       retries: 5
   etcd-0:
-    image: "quay.io/coreos/etcd:v3.5.7-arm64"
-#    image: "quay.io/coreos/etcd:latest"
+    image: "quay.io/coreos/etcd:v3.5.7"
     command:
       - /usr/local/bin/etcd
       - "--listen-client-urls"
@@ -154,7 +153,7 @@ services:
     environment:
       RUST_BACKTRACE: "1"
       # If ENABLE_TELEMETRY is not set, telemetry will start by default
-      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY}
+      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY:-true}
     container_name: frontend-node-0
     healthcheck:
       test:
@@ -226,7 +225,7 @@ services:
     environment:
       RUST_BACKTRACE: "1"
       # If ENABLE_TELEMETRY is not set, telemetry will start by default
-      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY}
+      ENABLE_TELEMETRY: ${ENABLE_TELEMETRY:-true}
     container_name: meta-node-0
     healthcheck:
       test: