envoy: Getting permission denied on latest dev image for access logs

- filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: envoy_egress
          upgrade_configs:
          - upgrade_type: "CONNECT"          
          access_log:
            name: envoy.file_access_log
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
              path: /dev/stdout

When the envoy-dev container is started it gives out following error, can someone help out here.

proxy_1        | [2020-06-11 06:29:12.117][6][critical][main] [source/server/server.cc:100] error initializing configuration '/etc/envoy/envoy.yaml': unable to open file '/dev/stdout': Permission denied
proxy_1        | [2020-06-11 06:29:12.130][6][info][main] [source/server/server.cc:685] exiting
proxy_1        | unable to open file '/dev/stdout': Permission denied

Image: envoyproxy/envoy-dev:92e608f066b017d664d8fa161cfc735f0c6b41e7

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 20 (9 by maintainers)

Most upvoted comments

This is related to the change introduced in #11323. I think you can either let the envoy user have access to /dev/stdout or set ENVOY_UID=0 when running the container.

dio on Jun 11, 2020

Ive been breaking my head over this for a while now. It runs fine in my local docker build, but when I deploy the container to cloud run this happens. Is there a way I could connect with you and show you whats happening ? @phlax I would really appreciate that. Thanks again

I’m running into this same issue trying to run Envoy on Cloud Run. Did you got it working?

pablote on Jun 24, 2021

I get this error when I deploy the container image to Google Cloud Run. Local container runs, but on cloud run it throws chown: changing ownership of '/dev/stdout': Operation not permitted

Any leads on this please ?

AkhilRaja on Jun 6, 2021

Setting ENVOY_UID as an env var as suggested previously worked for me

pablocompagni-contractorvp on Mar 30, 2022