upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor synced 2025-04-22 04:35:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

add --insucure-registry option to user_guide

Browse Source
This commit is contained in:
Wenkai Yin 2016-03-22 18:09:03 +08:00
parent 171028aef5
commit c83412e537
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/user_guide.md
View File

@ -72,7 +72,17 @@ Administrator can add "SysAdmin" role to an ordinary user by toggling the switch
![browse project](img/set_admin_remove_user.png) ![browse project](img/set_admin_remove_user.png)
##Pulling and pushing images using Docker client ##Pulling and pushing images using Docker client
**NOTE: Harbor only supports Registry V2 API. You need to use Docker client 1.6.0 or higher.** **NOTE: Harbor only supports Registry V2 API. You need to use Docker client 1.6.0 or higher.**
If you encounter an error as below when you pull or push images, you need to add '--insecure-registry' option to /etc/default/docker (ubuntu) or /etc/sysconfig/docker (centos):
*FATA[0000] Error response from daemon: v1 ping attempt failed with error:
Get https://myregistrydomain.com:5000/v1/_ping: tls: oversized record received with length 20527.
If this private registry supports only HTTP or HTTPS with an unknown CA certificate,please add
`--insecure-registry myregistrydomain.com:5000` to the daemon's arguments.
In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag;
simply place the CA certificate at /etc/docker/certs.d/myregistrydomain.com:5000/ca.crt*
###Pulling images ###Pulling images
If the project that the image belongs to is private, you should sign in first: If the project that the image belongs to is private, you should sign in first: