Skip to content

fix(containerImages): restrict local build contexts - #238

Draft
AzureMike wants to merge 1 commit into
radius-project:mainfrom
AzureMike:feature/container-images-local-context-security
Draft

fix(containerImages): restrict local build contexts#238
AzureMike wants to merge 1 commit into
radius-project:mainfrom
AzureMike:feature/container-images-local-context-security

Conversation

@AzureMike

Copy link
Copy Markdown
Contributor

Summary

Restricts local container image build contexts to /var/radius/build-contexts. This prevents builds from accessing registry credentials in the Terraform working directory.

Git build sources are unchanged.

Fixes #231

Question

@willdavsmith, should we address this, or is the current behavior acceptable? The issue only affects local builds, but a developer who controls the build context and Dockerfile can copy files available to dynamic-rp, including registry credentials.

Pros: Local builds can only access files the platform engineer places under /var/radius/build-contexts. Git builds are unchanged.

Cons: I think the Radius Helm chart cannot mount this directory through its values today. Local builds would require a custom chart or Deployment patch, plus a volume containing the source. Existing local paths outside this directory will stop working.

Signed-off-by: Mike Azure <mikeazure+microsoft@microsoft.com>
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.

Terraform containerImages can leak registry credentials through local build context

1 participant