Fixed
Status Update
No update yet.
Comments
fa...@google.com
Thanks for your report. I have forwarded this issue to the backend team. We will update this issue with any progress updates and a resolution.
fa...@google.com
su...@gmail.com
What's current status?
This does not need to be fixed immediately, but it would be appreciated if you can provide ETA, so that containerd community can determine whether containerd should implement the workaround.
This does not need to be fixed immediately, but it would be appreciated if you can provide ETA, so that containerd community can determine whether containerd should implement the workaround.
kl...@google.com
The fix will be rolled out by end of this week.
su...@gmail.com
The issue seems fixed, thank you
kl...@google.com
ni...@gmail.com
su...@gmail.com
Can anybody please remove the spam comment above (Jun 11, 2018 03:05AM) ?
Description
$ curl -i
HTTP/1.1 403 Forbidden
Docker-Distribution-API-Version: registry/2.0
Content-Type: application/json
Date: Tue, 08 Aug 2017 05:25:09 GMT
Server: Docker Registry
Cache-Control: private
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Accept-Ranges: none
Vary: Accept-Encoding
Transfer-Encoding: chunked
{"errors":[{"code":"DENIED","message":"Permission denied for \"${manifest}\" from request \"/v2/${project}/${image}/manifests/${manifest}\". "}]}
However, according to a Docker Registry maintainer, the above request should rather return 401 with `WWW-Authenticate` header.