Skip to content

Use podman native secrets for proxy container credentials#185

Merged
bbrowning merged 1 commit intomainfrom
paude-proxy-podman-secrets
Apr 3, 2026
Merged

Use podman native secrets for proxy container credentials#185
bbrowning merged 1 commit intomainfrom
paude-proxy-podman-secrets

Conversation

@bbrowning
Copy link
Copy Markdown
Owner

Proxy container credentials (API keys, tokens) were passed as plain
-e KEY=VALUE env vars, making them visible in podman inspect and
/proc//environ. Switch to podman's --secret type=env mechanism
which injects secrets as env vars inside the container without
exposing them externally. Docker falls back to -e flags since it
lacks standalone secret support.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Proxy container credentials (API keys, tokens) were passed as plain
-e KEY=VALUE env vars, making them visible in podman inspect and
/proc/<pid>/environ. Switch to podman's --secret type=env mechanism
which injects secrets as env vars inside the container without
exposing them externally. Docker falls back to -e flags since it
lacks standalone secret support.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@bbrowning bbrowning merged commit b181102 into main Apr 3, 2026
6 checks passed
@bbrowning bbrowning deleted the paude-proxy-podman-secrets branch April 3, 2026 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant