summaryrefslogtreecommitdiff
path: root/doc/user/project/container_registry.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/project/container_registry.md')
-rw-r--r--doc/user/project/container_registry.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/project/container_registry.md b/doc/user/project/container_registry.md
index cac64fc0cb6..eb9e1cd85cd 100644
--- a/doc/user/project/container_registry.md
+++ b/doc/user/project/container_registry.md
@@ -283,9 +283,9 @@ In the example above, we see the following trace on the mitmproxy window:
The above image shows:
-* The initial PUT requests went through fine with a 201 status code.
-* The 201 redirected the client to the S3 bucket.
-* The HEAD request to the AWS bucket reported a 403 Unauthorized.
+- The initial PUT requests went through fine with a 201 status code.
+- The 201 redirected the client to the S3 bucket.
+- The HEAD request to the AWS bucket reported a 403 Unauthorized.
What does this mean? This strongly suggests that the S3 user does not have the right
[permissions to perform a HEAD request](http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectHEAD.html).