gloo-envoy-wrapper container doesn't start with the Docker consul example

[nickcodefresh]

Gloo Edge Version

1.10.x (latest stable)

Kubernetes Version

No response

Describe the bug

Hi,

I'm trying to run the example project https://github.com/solo-io/gloo/tree/master/install/docker-compose-consul but am finding that the gloo-envoy-wrapper container continually restarts. This is what I see in the logs:

gateway-proxy_1  | [2022-01-21 16:49:05.814][1][info][main] [external/envoy/source/server/server.cc:393]   request trailer map: 136 bytes:
gateway-proxy_1  | [2022-01-21 16:49:05.814][1][info][main] [external/envoy/source/server/server.cc:393]   response header map: 432 bytes: :status,access-control
-allow-credentials,access-control-allow-headers,access-control-allow-methods,access-control-allow-origin,access-control-expose-headers,access-control-max-age,age,cache-
control,connection,content-encoding,content-length,content-type,date,etag,expires,grpc-message,grpc-status,keep-alive,last-modified,location,proxy-connection,server,tra
nsfer-encoding,upgrade,vary,via,x-envoy-attempt-count,x-envoy-decorator-operation,x-envoy-degraded,x-envoy-immediate-health-check-fail,x-envoy-ratelimited,x-envoy-upstr
eam-canary,x-envoy-upstream-healthchecked-cluster,x-envoy-upstream-service-time,x-request-id
gateway-proxy_1  | [2022-01-21 16:49:05.814][1][info][main] [external/envoy/source/server/server.cc:393]   response trailer map: 160 bytes: grpc-message,grpc-sta
tus
gateway-proxy_1  | [2022-01-21 16:49:05.815][1][info][main] [external/envoy/source/server/server.cc:740] runtime: {}
gateway-proxy_1  | [2022-01-21 16:49:05.815][1][info][admin] [external/envoy/source/server/admin/admin.cc:135] admin address: 0.0.0.0:19000
gateway-proxy_1  | [2022-01-21 16:49:05.816][1][info][config] [external/envoy/source/server/configuration_impl.cc:127] loading tracing configuration
gateway-proxy_1  | [2022-01-21 16:49:05.816][1][info][config] [external/envoy/source/server/configuration_impl.cc:87] loading 0 static secret(s)
gateway-proxy_1  | [2022-01-21 16:49:05.816][1][info][config] [external/envoy/source/server/configuration_impl.cc:93] loading 1 cluster(s)
gateway-proxy_1  | [2022-01-21 16:49:05.817][1][warning][misc] [external/envoy/source/common/config/utility.h:204] V2 (and AUTO) xDS transport protocol versions
are deprecated in api_type: GRPC
gateway-proxy_1  | grpc_services {
gateway-proxy_1  |   envoy_grpc {
gateway-proxy_1  |     cluster_name: "xds_cluster"
gateway-proxy_1  |   }
gateway-proxy_1  | }
gateway-proxy_1  | . The v2 xDS major version is deprecated and disabled by default. Support for v2 will be removed from Envoy at the start of Q1 2021. You may m
ake use of v2 in Q4 2020 by following the advice in https://www.envoyproxy.io/docs/envoy/latest/faq/api/transition.
gateway-proxy_1  | [2022-01-21 16:49:05.817][1][critical][main] [external/envoy/source/server/server.cc:114] error initializing configuration '/config/envoy.yaml
': V2 (and AUTO) xDS transport protocol versions are deprecated in api_type: GRPC
gateway-proxy_1  | grpc_services {
gateway-proxy_1  |   envoy_grpc {
gateway-proxy_1  |     cluster_name: "xds_cluster"
gateway-proxy_1  |   }
gateway-proxy_1  | }
gateway-proxy_1  | . The v2 xDS major version is deprecated and disabled by default. Support for v2 will be removed from Envoy at the start of Q1 2021. You may m
ake use of v2 in Q4 2020 by following the advice in https://www.envoyproxy.io/docs/envoy/latest/faq/api/transition.
gateway-proxy_1  | [2022-01-21 16:49:05.818][1][info][main] [external/envoy/source/server/server.cc:891] exiting
gateway-proxy_1  | V2 (and AUTO) xDS transport protocol versions are deprecated in api_type: GRPC
gateway-proxy_1  | grpc_services {
gateway-proxy_1  |   envoy_grpc {
gateway-proxy_1  |     cluster_name: "xds_cluster"
gateway-proxy_1  |   }
gateway-proxy_1  | }
gateway-proxy_1  | . The v2 xDS major version is deprecated and disabled by default. Support for v2 will be removed from Envoy at the start of Q1 2021. You may m
ake use of v2 in Q4 2020 by following the advice in https://www.envoyproxy.io/docs/envoy/latest/faq/api/transition.

File logs are attached
log.txt

Steps to reproduce the bug

Just start the containers as indicated in https://docs.solo.io/gloo-edge/latest/installation/gateway/development/docker-compose-consul/

I'm running

Docker version 20.10.12, build e91ed57
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal

Expected Behavior

Container should start succesfully.

Additional Context

No response