Bump compose to use gateway_invoke for nats-queue-worker

This change means the gateway is used to invoke functions
asynchronously rather than directly so that the scale from zero
path can execute.

Signed-off-by: Alex Ellis <alexellis2@gmail.com>

docker-compose.arm64.yml

@@ -52,6 +52,8 @@ services:
             DOCKER_API_VERSION: "1.30"
             basic_auth: "${BASIC_AUTH:-true}"
             secret_mount_path: "/run/secrets/"
+            gateway_invoke: "true"
+            faas_gateway_address: "gateway"
         deploy:
             placement:
                 constraints:

docker-compose.armhf.yml

@@ -100,6 +100,8 @@ services:
             ack_wait: "5m5s"    # Max duration of any async task / request
             basic_auth: "${BASIC_AUTH:-true}"
             secret_mount_path: "/run/secrets/"
+            gateway_invoke: "true"
+            faas_gateway_address: "gateway"
         deploy:
             resources:
                 limits:

docker-compose.yml

@@ -92,14 +92,16 @@ services:
                     - "node.platform.os == linux"
 
     queue-worker:
-        image: openfaas/queue-worker:0.7.1
+        image: openfaas/queue-worker:0.7.2
         networks:
             - functions
         environment:
             max_inflight: "1"
             ack_wait: "5m5s" # Max duration of any async task / request
             basic_auth: "${BASIC_AUTH:-true}"
             secret_mount_path: "/run/secrets/"
+            gateway_invoke: "true"
+            faas_gateway_address: "gateway"
         deploy:
             resources:
                 limits: