Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi <#C012RBW0F18|hydra>,
How do I set env variables inside a running container?
I tried following this answer on stackoverflow <https://stackoverflow.com/a/30120197/5940139>
But it returns error saying
```OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown```
I tried inspecting docker image to find out the path for Cmd but I can't see Cmdover there.

at some places it was recommended to use sh instead of /bin/bash
It didn't set the env values though.

Hi <@U02L8J8RRTQ>,

If you're using k8s to deploy your containers, then you can $ kubectl set env &lt;deployment&gt; &lt;env_var&gt;=&lt;value&gt; e.g. $ kubectl set env deployment/my-hydra LOG_LEAK_SENSITIVE_VALUES=true. Then run $ kubectl set env pods --all --list to verify your new env var is set. Note that you must set env on the deployment, as the pod is read-only.

If you're using docker-compose, I haven't tried it but this page might help: <https://docs.docker.com/compose/environment-variables/>