Docker sandboxes support secret injection. https://docs.docker.com/reference/cli/sbx/secret/set/
exactly, i don't know why everyone is ignoring this. It's the obvious solution to at least 80% of what most posters here are complaining about and comes built in already in multiple existing solutions.
I use these exclusively now. I very very rarely run outside of an sbx. Works great.
From https://docs.docker.com/reference/cli/sbx/secret/set-custom/
> Custom secrets work via a placeholder: the sandbox sees the placeholder value instead of the real secret. When the sandbox makes an outbound request to the target host, the proxy replaces the placeholder with the real secret in the request headers — the secret never enters the sandbox directly.