From 3c3f9411e17ae8a26fe8af4b2d751e8cf31f1b31 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Mon, 18 Mar 2019 17:24:15 -0700 Subject: [PATCH 1/2] Additional error for troubleshooting section Addresses #8445 . --- .../sign-images/trust-with-remote-ucp.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md b/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md index e5eaf576bb..7539154616 100644 --- a/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md +++ b/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md @@ -226,6 +226,7 @@ Orchestrator as there is no SSO between cluster 2 and DTR. See the relevant ### Example Errors +#### Image or trust data does not exist ``` image or trust data does not exist for dtr.example.com/admin/trustdemo:1 ``` @@ -233,6 +234,8 @@ image or trust data does not exist for dtr.example.com/admin/trustdemo:1 This means something went wrong when initiating the repository or signing the image, as the tag contains no signing data. +#### Image did not meet required signing policy + ``` Error response from daemon: image did not meet required signing policy @@ -243,6 +246,14 @@ This means that the image was signed correctly, however the user who signed the image does not meet the signing policy in cluster 2. This could be because you signed the image with the wrong user keys. +#### DTR URL must be a registered trusted registry + +``` +Error response from daemon: dtr.example.com must be a registered trusted registry. See 'docker run --help'. +``` + +This means you have not registered DTR to work with a remote UCP instance yet, as outlined in [Registering DTR with a Remote Universal Control Plane](#registering-dtr-with-a-remote-universal-control-plane). + ## Where to go next - [Learn more about Notary](/notary/advanced_usage.md) From 65a8901f505c7b1948c5cc8d46f34f709747e1f5 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Tue, 19 Mar 2019 11:32:54 -0700 Subject: [PATCH 2/2] Remove extraneous info --- ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md b/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md index 7539154616..3d15f2cb79 100644 --- a/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md +++ b/ee/dtr/user/manage-images/sign-images/trust-with-remote-ucp.md @@ -249,7 +249,7 @@ signed the image with the wrong user keys. #### DTR URL must be a registered trusted registry ``` -Error response from daemon: dtr.example.com must be a registered trusted registry. See 'docker run --help'. +Error response from daemon: dtr.example.com must be a registered trusted registry. ``` This means you have not registered DTR to work with a remote UCP instance yet, as outlined in [Registering DTR with a Remote Universal Control Plane](#registering-dtr-with-a-remote-universal-control-plane).