registry placement auth.token After the configuration is completed, you can use docker login or register normally, but the API interface for tuning is directly presented. Authentication required #4348
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
registry placement auth.token
After the configuration is completed, you can use docker login or register normally, but the API interface for tuning is directly presented. Authentication required
curl -v --basic -u xxx:xxxx 127.0.0.1:5000/v2/_catalog
< HTTP/1.1 401 Unauthorized
< Content-Type: application/json; charset=utf-8
< Docker-Distribution-Api-Version: registry/2.0
< Www-Authenticate: Bearer realm="http://192.168.207.156:8080/registry/auth",service="sitonai",scope="registry:catalog:"
< Date: Tue, 14 May 2024 02:33:11 GMT
< Content-Length: 145
<
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"registry","Class":"","Name":"catalog","Action":""}]}]}
config.yaml
version: 0.1
log:
level: debug
fields:
service: registry
storage:
cache:
blobdescriptor: inmemory
filesystem:
rootdirectory: /var/lib/registry
maintenance:
uploadpurging:
enabled: false
delete:
enabled: true
http:
addr: :5000
secret: placeholder
debug:
addr: localhost:5001
auth:
token:
realm: http://192.168.207.156:8080/registry/auth
service: 192.168.207.156
issuer: xxxxx
rootcertbundle: /registry/auth.crt
validation:
disabled: true
compatibility:
schema1:
enabled: true
Beta Was this translation helpful? Give feedback.
All reactions