Envoy: Front-Envoy example not working anymore

[githubYasser]

Bug Template

Title: Front-Envoy example is not working anymore

Description:

Im starting the services with docker-compose up. They are not starting.`

Logs:

docker-compose up
Creating network "front-proxy_envoymesh" with the default driver
Creating front-proxy_service1_1 ... done
Creating front-proxy_service2_1 ... done
Creating front-proxy_front-envoy_1 ... done
Attaching to front-proxy_service1_1, front-proxy_service2_1, front-proxy_front-envoy_1
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:202] initializing epoch 0 (hot restart version=10.200.16384.127.options=capacity=16384, num_slots=8209 hash=228984379728933363 size=2654312)
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:204] statically linked extensions:
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:206] access_loggers: envoy.file_access_log,envoy.http_grpc_access_log
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:209] filters.http: envoy.buffer,envoy.cors,envoy.ext_authz,envoy.fault,envoy.filters.http.header_to_metadata,envoy.filters.http.jwt_authn,envoy.filters.http.rbac,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:212] filters.listener: envoy.listener.original_dst,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:215] filters.network: envoy.client_ssl_auth,envoy.echo,envoy.ext_authz,envoy.filters.network.rbac,envoy.filters.network.sni_cluster,envoy.filters.network.thrift_proxy,envoy.http_connection_manager,envoy.mongo_proxy,envoy.ratelimit,envoy.redis_proxy,envoy.tcp_proxy
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:217] stat_sinks: envoy.dog_statsd,envoy.metrics_service,envoy.stat_sinks.hystrix,envoy.statsd
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:219] tracers: envoy.dynamic.ot,envoy.lightstep,envoy.zipkin
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:222] transport_sockets.downstream: envoy.transport_sockets.capture,raw_buffer,tls
service1_1 | [2018-10-08 13:33:43.036][7][info][main] source/server/server.cc:225] transport_sockets.upstream: envoy.transport_sockets.capture,raw_buffer,tls
service1_1 | [2018-10-08 13:33:43.037][7][critical][main] source/server/server.cc:80] error initializing configuration '/etc/service-envoy.yaml': Unable to convert YAML as JSON:
service1_1 | [2018-10-08 13:33:43.037][7][info][main] source/server/server.cc:492] exiting
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:202] initializing epoch 0 (hot restart version=10.200.16384.127.options=capacity=16384, num_slots=8209 hash=228984379728933363 size=2654312)
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:204] statically linked extensions:
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:206] access_loggers: envoy.file_access_log,envoy.http_grpc_access_log
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:209] filters.http: envoy.buffer,envoy.cors,envoy.ext_authz,envoy.fault,envoy.filters.http.header_to_metadata,envoy.filters.http.jwt_authn,envoy.filters.http.rbac,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:212] filters.listener: envoy.listener.original_dst,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:215] filters.network: envoy.client_ssl_auth,envoy.echo,envoy.ext_authz,envoy.filters.network.rbac,envoy.filters.network.sni_cluster,envoy.filters.network.thrift_proxy,envoy.http_connection_manager,envoy.mongo_proxy,envoy.ratelimit,envoy.redis_proxy,envoy.tcp_proxy
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:217] stat_sinks: envoy.dog_statsd,envoy.metrics_service,envoy.stat_sinks.hystrix,envoy.statsd
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:219] tracers: envoy.dynamic.ot,envoy.lightstep,envoy.zipkin
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:222] transport_sockets.downstream: envoy.transport_sockets.capture,raw_buffer,tls
service2_1 | [2018-10-08 13:33:43.596][7][info][main] source/server/server.cc:225] transport_sockets.upstream: envoy.transport_sockets.capture,raw_buffer,tls
service2_1 | [2018-10-08 13:33:43.597][7][critical][main] source/server/server.cc:80] error initializing configuration '/etc/service-envoy.yaml': Unable to convert YAML as JSON:
service2_1 | [2018-10-08 13:33:43.597][7][info][main] source/server/server.cc:492] exiting
front-proxy_service1_1 exited with code 1
front-envoy_1 | [2018-10-08 13:33:45.073][7][info][main] source/server/server.cc:202] initializing epoch 0 (hot restart version=10.200.16384.127.options=capacity=16384, num_slots=8209 hash=228984379728933363 size=2654312)
front-envoy_1 | [2018-10-08 13:33:45.073][7][info][main] source/server/server.cc:204] statically linked extensions:
front-envoy_1 | [2018-10-08 13:33:45.073][7][info][main] source/server/server.cc:206] access_loggers: envoy.file_access_log,envoy.http_grpc_access_log
front-envoy_1 | [2018-10-08 13:33:45.074][7][info][main] source/server/server.cc:209] filters.http: envoy.buffer,envoy.cors,envoy.ext_authz,envoy.fault,envoy.filters.http.header_to_metadata,envoy.filters.http.jwt_authn,envoy.filters.http.rbac,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
front-envoy_1 | [2018-10-08 13:33:45.074][7][info][main] source/server/server.cc:212] filters.listener: envoy.listener.original_dst,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
front-envoy_1 | [2018-10-08 13:33:45.074][7][info][main] source/server/server.cc:215] filters.network: envoy.client_ssl_auth,envoy.echo,envoy.ext_authz,envoy.filters.network.rbac,envoy.filters.network.sni_cluster,envoy.filters.network.thrift_proxy,envoy.http_connection_manager,envoy.mongo_proxy,envoy.ratelimit,envoy.redis_proxy,envoy.tcp_proxy
front-envoy_1 | [2018-10-08 13:33:45.074][7][info][main] source/server/server.cc:217] stat_sinks: envoy.dog_statsd,envoy.metrics_service,envoy.stat_sinks.hystrix,envoy.statsd
front-envoy_1 | [2018-10-08 13:33:45.075][7][info][main] source/server/server.cc:219] tracers: envoy.dynamic.ot,envoy.lightstep,envoy.zipkin
front-envoy_1 | [2018-10-08 13:33:45.075][7][info][main] source/server/server.cc:222] transport_sockets.downstream: envoy.transport_sockets.capture,raw_buffer,tls
front-envoy_1 | [2018-10-08 13:33:45.075][7][info][main] source/server/server.cc:225] transport_sockets.upstream: envoy.transport_sockets.capture,raw_buffer,tls
front-envoy_1 | [2018-10-08 13:33:45.112][7][critical][main] source/server/server.cc:80] error initializing configuration '/etc/front-envoy.yaml': Unable to convert YAML as JSON:
front-envoy_1 | [2018-10-08 13:33:45.112][7][info][main] source/server/server.cc:492] exiting
front-proxy_service2_1 exited with code 1
front-proxy_front-envoy_1 exited with code 1

thanks

[githubYasser]

Hi,

we can close this issue. The problem was because of docker-compose.

Im using docker Version: 18.06.1-ce.
My docker-compose version is 1.22.0.

One have to change following things so that this works:
According to docker-compose ducumentation for docker-engine 18.06.0+ we have to change the compose file format to 3.7 (https://docs.docker.com/compose/compose-file/)
In the example the compose file format version was "2".

The second change i made inside the docker-compose file. The volumes section of a service has to be changed. For example for service2 the change is :

service2:
#volumes:
#- ./service-envoy.yaml:/etc/service-envoy.yaml
volumes:
- type: volume
source: test # name of the folder where your envoy configuration is
target: /etc/
volume:
nocopy: false
build:
context: .
dockerfile: Dockerfile-service
expose:
- "80"
volumes:
test:

[52tt]

I jumped to https://docs.docker.com/compose/compose-file/ and found the example they provided is exactly similar to what we have under envoy-front/.
Did I miss something?

[rinormaloku]

I had the same problem on Windows using Windows Linux Subsystem.

WSL was not able to map the file and it was being mapped as a directory. Solution: I switched to Powershell.

Though in Powershell I had the infamous problem with files being CRLF instead of LF. Solution: Change the eol of the files to LF.

[prakasa-tkpd]

Still got this issue using

Docker version 19.03.5, build 633a0ea
docker-compose version 1.24.1, build 4667896b