From ff81152728ce56340dd98ef805003cf7f086bbf4 Mon Sep 17 00:00:00 2001 From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com> Date: Wed, 7 Nov 2018 10:16:52 -0800 Subject: [PATCH] Update content_trust.md --- engine/security/trust/content_trust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/security/trust/content_trust.md b/engine/security/trust/content_trust.md index 0ef505081c..21ffcd0b4c 100644 --- a/engine/security/trust/content_trust.md +++ b/engine/security/trust/content_trust.md @@ -183,7 +183,7 @@ The signature verification feature is configured in the Docker daemon configurat
trust-pinning:library-images
docker.io/library/*<\code>) to the hard-coded Docker official images root key. DCT trusts the official images by default. This is in addition to whatever images are specified by trust-pinning:root-keys<\code>. If `trustpinning:root-keys` specifies a key mapping for docker.io/library/*
, those keys will be preferred for trust pinning. Otherwise, if a more general docker.io/*
or *
are specified, the official images key will be preferred.
docker.io/library/*
) to the hard-coded Docker official images root key. DCT trusts the official images by default. This is in addition to whatever images are specified by trust-pinning:root-keys<\code>. If `trustpinning:root-keys` specifies a key mapping for docker.io/library/*
, those keys will be preferred for trust pinning. Otherwise, if a more general docker.io/*
or *
are specified, the official images key will be preferred.
allow-expired-trust-cache