examples: standardize docker-compose version and yaml extension

docs/root/start/sandboxes/front_proxy.rst

@@ -16,7 +16,7 @@ Below you can see a graphic showing the docker compose deployment:
 
 All incoming requests are routed via the front Envoy, which is acting as a reverse proxy sitting on
 the edge of the ``envoymesh`` network. Port ``80`` is mapped to  port ``8000`` by docker compose
-(see :repo:`/examples/front-proxy/docker-compose.yml`). Moreover, notice
+(see :repo:`/examples/front-proxy/docker-compose.yaml`). Moreover, notice
 that all  traffic routed by the front Envoy to the service containers is actually routed to the
 service Envoys (routes setup in :repo:`/examples/front-proxy/front-envoy.yaml`). In turn the service
 envoys route the  request to the flask app via the loopback address (routes setup in

docs/root/start/sandboxes/grpc_bridge.rst

@@ -23,10 +23,10 @@ To build the Go gRPC service run::
 
   $ pwd
   envoy/examples/grpc-bridge
-  $ script/bootstrap
-  $ script/build
+  $ script/bootstrap.sh
+  $ script/build.sh
 
-Note: ``build`` requires that your Envoy codebase (or a working copy thereof) is in ``$GOPATH/src/github.com/envoyproxy/envoy``.
+Note: ``build.sh`` requires that your Envoy codebase (or a working copy thereof) is in ``$GOPATH/src/github.com/envoyproxy/envoy``.
 
 Docker compose
 ~~~~~~~~~~~~~~

docs/root/start/sandboxes/jaeger_native_tracing.rst

@@ -22,7 +22,7 @@ only works on x86-64).
 
 All incoming requests are routed via the front Envoy, which is acting as a reverse proxy
 sitting on the edge of the ``envoymesh`` network. Port ``80`` is mapped to  port ``8000``
-by docker compose (see :repo:`/examples/jaeger-native-tracing/docker-compose.yml`). Notice that
+by docker compose (see :repo:`/examples/jaeger-native-tracing/docker-compose.yaml`). Notice that
 all Envoys are configured to collect request traces (e.g., http_connection_manager/config/tracing setup in
 :repo:`/examples/jaeger-native-tracing/front-envoy-jaeger.yaml`) and setup to propagate the spans generated
 by the Jaeger tracer to a Jaeger cluster (trace driver setup

docs/root/start/sandboxes/jaeger_tracing.rst

@@ -11,7 +11,7 @@ The three containers will be deployed inside a virtual network called ``envoymes
 
 All incoming requests are routed via the front Envoy, which is acting as a reverse proxy
 sitting on the edge of the ``envoymesh`` network. Port ``80`` is mapped to  port ``8000``
-by docker compose (see :repo:`/examples/jaeger-tracing/docker-compose.yml`). Notice that
+by docker compose (see :repo:`/examples/jaeger-tracing/docker-compose.yaml`). Notice that
 all Envoys are configured to collect request traces (e.g., http_connection_manager/config/tracing setup in
 :repo:`/examples/jaeger-tracing/front-envoy-jaeger.yaml`) and setup to propagate the spans generated
 by the Jaeger tracer to a Jaeger cluster (trace driver setup

docs/root/start/sandboxes/zipkin_tracing.rst

@@ -11,7 +11,7 @@ The three containers will be deployed inside a virtual network called ``envoymes
 
 All incoming requests are routed via the front Envoy, which is acting as a reverse proxy
 sitting on the edge of the ``envoymesh`` network. Port ``80`` is mapped to  port ``8000``
-by docker compose (see :repo:`/examples/zipkin-tracing/docker-compose.yml`). Notice that
+by docker compose (see :repo:`/examples/zipkin-tracing/docker-compose.yaml`). Notice that
 all Envoys are configured to collect request traces (e.g., http_connection_manager/config/tracing setup in
 :repo:`/examples/zipkin-tracing/front-envoy-zipkin.yaml`) and setup to propagate the spans generated
 by the Zipkin tracer to a Zipkin cluster (trace driver setup

examples/cors/backend/docker-compose.yml → examples/cors/backend/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   front-envoy:

examples/cors/frontend/docker-compose.yml → examples/cors/frontend/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   front-envoy:

examples/fault-injection/docker-compose.yml → examples/fault-injection/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
   envoy:
     build:

examples/front-proxy/docker-compose.yml → examples/front-proxy/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '3.7'
+version: "3.7"
 services:
 
   front-envoy:

examples/grpc-bridge/Dockerfile-grpc

@@ -2,6 +2,6 @@ FROM envoyproxy/envoy-dev:latest
 
 RUN mkdir /var/log/envoy/
 COPY ./bin/service /usr/local/bin/srv
-COPY ./script/grpc_start /etc/grpc_start
+COPY ./script/grpc_start.sh /etc/grpc_start
 CMD /etc/grpc_start
 

examples/grpc-bridge/docker-compose.yml → examples/grpc-bridge/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   python:

examples/jaeger-native-tracing/docker-compose.yml → examples/jaeger-native-tracing/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   front-envoy:

examples/jaeger-tracing/docker-compose.yml → examples/jaeger-tracing/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   front-envoy:

examples/lua/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   proxy:

examples/mysql/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '3.5'
+version: "3.7"
 services:
 
   proxy:

examples/redis/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   proxy:

examples/zipkin-tracing/docker-compose.yml → examples/zipkin-tracing/docker-compose.yaml

@@ -1,4 +1,4 @@
-version: '2'
+version: "3.7"
 services:
 
   front-envoy: