From 22c0665d19f15d51cc6fe270fe664df27f82c985 Mon Sep 17 00:00:00 2001 From: Samuel K Date: Thu, 12 Nov 2026 04:52:43 -0600 Subject: [PATCH] docs: state that runArgs is not checked against reserved labels --- .../docs/developing-in-workspaces/devcontainer-json.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx index 01303c9cd..00000fd91 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx @@ -167,4 +167,6 @@ Do not supply these keys through `--id-label`, Kubernetes provider labels, or Ku Custom identification labels, including `dev.containers.id`, remain configurable. The `devcontainer.metadata` image label remains a supported configuration source and can contain private values. Reserving a label does not make every value stored under it public. -The top-level `containerLabels` and `labels` fields in devcontainer.json are ignored. External providers reject `runArgs` rather than translate them into request labels. Native Docker, Podman, nerdctl, Apple and Compose arguments and inherited image labels are outside this explicit map reservation. Avoid using reserved keys there. Native argument validation is a separate follow-up. +The top-level `containerLabels` and `labels` fields in devcontainer.json are ignored. External providers reject `runArgs` rather than translate them into request labels. + +For Docker, Podman, nerdctl, Apple and Compose, `runArgs`, Compose arguments and inherited image labels are passed to the runtime and are not checked against this reservation. `runArgs` can already set any container option, including labels, privileges and mounts, so it is not a security boundary. Do not use reserved keys there, and only open a devcontainer.json you trust.