From ae8068f22f4b342f11200bb2ff6ea963c45048aa Mon Sep 17 00:00:00 2001 From: Vivek Saraswat Date: Tue, 31 Oct 2017 09:53:24 -0700 Subject: [PATCH] Run only signed images change (#5172) * Run only signed images change It turns out the "run only signed images" feature only works by selecting teams in the `docker-datacenter` org. This became an issue in UCP 2.2 which has multiple org support. --- .../admin/configure/run-only-the-images-you-trust.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/datacenter/ucp/2.2/guides/admin/configure/run-only-the-images-you-trust.md b/datacenter/ucp/2.2/guides/admin/configure/run-only-the-images-you-trust.md index 5e7392c4ff..6d2a567cf4 100644 --- a/datacenter/ucp/2.2/guides/admin/configure/run-only-the-images-you-trust.md +++ b/datacenter/ucp/2.2/guides/admin/configure/run-only-the-images-you-trust.md @@ -43,12 +43,19 @@ With this setting, UCP allows deploying any image as long as the image has been signed. It doesn't matter who signed the image. To enforce that the image needs to be signed by specific teams, click the -dropdown and select those teams from the list. +dropdown and select those teams from the list. + +> Team must be in docker-datacenter +> +> You need to select a team that's part of the `docker-datacenter` organization +> in order to use this feature. +{: .important} ![UCP settings](../../images/run-only-the-images-you-trust-3.png){: .with-border} If you specify multiple teams, the image needs to be signed by a member of each -team, or someone that is a member of all those teams. +team, or someone that is a member of all those teams, again which must be a part +of the `docker-datacenter` organization. > Signing with teams >