部署Harbeor服务
Harbor 被部署为多个 Docker 容器，因此可以部署在任何支持 Docker 的 Linux 发行版 上。Harbor与rejistry区别
rejisty私有仓库：下载并加载为容器进行使用，里面存储镜像
Harbor可以使用多租户（多用户），以项目的形式把镜像进行分门别类的管理，并进行权限分配，若如一个操作系统服务端主机需要安装 Python、Docker 和 Docker Compose（容器编排）。（nignx系统上默认python2.6的版本）
实验环境
[root@server1 ~]# iptables -F
[root@server1 ~]# setenforce 0
安装docker-compose
将harbor文件拖入该目录下，并进行查看
[root@server1 ~]# ls
harbor-offline-installer-v1.2.2.tgz
将harbor-offline-installer-v1.2.2.tgz解压到/usr/local目录下
[root@server1 ~]# tar zxvf harbor-offline-installer-v1.2.2.tgz -C /usr/local/
到/usr./local查看是否有harbor文件
[root@server1 ~]# cd /usr/local/
[root@server1 local]# ls
harbor
修稿harbor配置文件
[root@server1 local]# cd harbor/
[root@server1 harbor]# ls
common docker-compose.notary.yml harbor_1_1_0_template harbor.v1.2.2.tar.gz LICENSE prepare
docker-compose.clair.yml docker-compose.yml harbor.cfg install.sh NOTICE upgrade
[root@server1 harbor]# vim harbor.cfg
4 #DO NOT use localhost or 127.0.0.1, because Harbor needs to be accessed by external clients.
5 hostname = 20.0.0.11 修改主机ip
59 harbor_admin_password = Harbor12345 初始密码（前面字母大写）
[root@server1 harbor]# vim docker-compose.yml //内部是各个容器的编排 这里不做修改
ports：仓库资源
将docker-compose脚本文件安装在/usr/local/bin/目录下，并添加执行权限
[root@server1 harbor]# cd /usr/local/bin/
[root@server1 bin]# rz -E
rz waiting to receive.
[root@server1 bin]# chmod +x docker-compose
[root@server1 bin]# ls
docker-compose
执行安装脚本
[root@server1 bin]# cd /usr/local/harbor/
[root@server1 harbor]# ./install.sh
Note: docker version: 19.03.13
Note: docker-compose version: 1.21.1
[Step 1]: loading Harbor images ...
dd60b611baaa: Loading layer [==================================================>] 133.2MB/133.2MB
abf0579c40fd: Loading layer [==================================================>] 1.536kB/1.536kB
ea1fc7bed9c5: Loading layer [==================================================>] 22.48MB/22.48MB
1d6671367c69: Loading layer [==================================================>] 7.168kB/7.168kB
b322bb3e4765: Loading layer [==================================================>] 5.339MB/5.339MB
0cf512d418ac: Loading layer [==================================================>] 9.728kB/9.728kB
4a7cdc0b1a2b: Loading layer [==================================================>] 2.56kB/2.56kB
ef1130526636: Loading layer [==================================================>] 22.48MB/22.48MB
Loaded image: vmware/harbor-ui:v1.2.2
4a050fccec52: Loading layer [==================================================>] 12.16MB/12.16MB
d918d73369ec: Loading layer [==================================================>] 17.3MB/17.3MB
22898836924e: Loading layer [==================================================>] 15.87kB/15.87kB
Loaded image: vmware/notary-photon:server-0.5.0
76c156eab077: Loading layer [==================================================>] 134MB/134MB
1eae6563289a: Loading layer [==================================================>] 16.42MB/16.42MB
Loaded image: vmware/nginx-photon:1.11.13
2e814f7ef645: Loading layer [==================================================>] 2.048kB/2.048kB
bc5742b580db: Loading layer [==================================================>] 2.048kB/2.048kB
5413bcdb81b0: Loading layer [==================================================>] 2.56kB/2.56kB
c4e2be066795: Loading layer [==================================================>] 3.584kB/3.584kB
a4ea62be60b0: Loading layer [==================================================>] 22.8MB/22.8MB
800a351ae5da: Loading layer [==================================================>] 22.8MB/22.8MB
Loaded image: vmware/registry:2.6.2-photon
Loaded image: photon:1.0
a39bd6a7f897: Loading layer [==================================================>] 10.95MB/10.95MB
6f79b8337a1f: Loading layer [==================================================>] 17.3MB/17.3MB
74bbd0e81dd0: Loading layer [==================================================>] 15.87kB/15.87kB
Loaded image: vmware/notary-photon:signer-0.5.0
2202528221a2: Loading layer [==================================================>] 7.07MB/7.07MB
4fe250d3c912: Loading layer [==================================================>] 7.07MB/7.07MB
Loaded image: vmware/harbor-adminserver:v1.2.2
9463fb852970: Loading layer [==================================================>] 75.37MB/75.37MB
d2c9a2a395d9: Loading layer [==================================================>] 3.584kB/3.584kB
b08aea2a8a82: Loading layer [==================================================>] 3.072kB/3.072kB
103e65a1013b: Loading layer [==================================================>] 3.072kB/3.072kB
Loaded image: vmware/harbor-log:v1.2.2
5d6cbe0dbcf9: Loading layer [==================================================>] 129.2MB/129.2MB
435f2dfbd884: Loading layer [==================================================>] 344.6kB/344.6kB
814d7b59f0cc: Loading layer [==================================================>] 4.657MB/4.657MB
aae399245bd0: Loading layer [==================================================>] 1.536kB/1.536kB
21e2ae955f72: Loading layer [==================================================>] 33.84MB/33.84MB
a2d0f7b84059: Loading layer [==================================================>] 25.09kB/25.09kB
819fa6af55b8: Loading layer [==================================================>] 3.584kB/3.584kB
78914c99a468: Loading layer [==================================================>] 167.7MB/167.7MB
36e79c658afb: Loading layer [==================================================>] 6.144kB/6.144kB
f73503aca003: Loading layer [==================================================>] 9.216kB/9.216kB
a21b39f6da59: Loading layer [==================================================>] 1.536kB/1.536kB
ef81eb7c77b3: Loading layer [==================================================>] 8.704kB/8.704kB
08d0cfe60b0d: Loading layer [==================================================>] 4.608kB/4.608kB
0864dda8f611: Loading layer [==================================================>] 4.608kB/4.608kB
Loaded image: vmware/harbor-db:v1.2.2
29d1f4ae97dd: Loading layer [==================================================>] 18.31MB/18.31MB
7caf936e1402: Loading layer [==================================================>] 18.31MB/18.31MB
Loaded image: vmware/harbor-jobservice:v1.2.2
78dbfa5b7cbc: Loading layer [==================================================>] 130.9MB/130.9MB
5f70bf18a086: Loading layer [==================================================>] 1.024kB/1.024kB
8deec01122be: Loading layer [==================================================>] 344.6kB/344.6kB
574ab36807f2: Loading layer [==================================================>] 1.536kB/1.536kB
d8f2cde2eef8: Loading layer [==================================================>] 20.48kB/20.48kB
eaa3924b054e: Loading layer [==================================================>] 5.12kB/5.12kB
8aa2c772121c: Loading layer [==================================================>] 184.3MB/184.3MB
c3014bbccb0b: Loading layer [==================================================>] 8.704kB/8.704kB
978a35efaa8c: Loading layer [==================================================>] 4.608kB/4.608kB
c2385ae7d6e5: Loading layer [==================================================>] 16.6MB/16.6MB
Loaded image: vmware/harbor-notary-db:mariadb-10.1.10
c192a34d4ff4: Loading layer [==================================================>] 155.2MB/155.2MB
d012a9276a83: Loading layer [==================================================>] 10.75MB/10.75MB
b8befd881cb5: Loading layer [==================================================>] 10.75MB/10.75MB
Loaded image: vmware/clair:v2.0.1-photon
bbda1562018e: Loading layer [==================================================>] 101.6MB/101.6MB
1171ab08cc04: Loading layer [==================================================>] 6.656kB/6.656kB
6df81d3a0683: Loading layer [==================================================>] 6.656kB/6.656kB
Loaded image: vmware/postgresql:9.6.4-photon
[Step 2]: preparing environment ...
Generated and saved secret to file: /data/secretkey
Generated configuration file: ./common/config/nginx/nginx.conf
Generated configuration file: ./common/config/adminserver/env
Generated configuration file: ./common/config/ui/env
Generated configuration file: ./common/config/registry/config.yml
Generated configuration file: ./common/config/db/env
Generated configuration file: ./common/config/jobservice/env
Generated configuration file: ./common/config/jobservice/app.conf
Generated configuration file: ./common/config/ui/app.conf
Generated certificate, key file: ./common/config/ui/private_key.pem, cert file: ./common/config/registry/root.crt
The configuration files are ready, please use docker-compose to start the service.
[Step 3]: checking existing instance of Harbor ...
[Step 4]: starting Harbor ...
Creating network "harbor_harbor" with the default driver
Creating harbor-log ... done
Creating harbor-db ... done
Creating harbor-adminserver ... done
Creating registry ... done
Creating harbor-ui ... done
Creating harbor-jobservice ... done
Creating nginx ... done
✔ ----Harbor has been installed and started successfully.----
Now you should be able to visit the admin portal at http://20.0.0.11.
For more details, please visit https://github.com/vmware/harbor .关于 Harbor.cfg 配置文件中有两类参数：所需参数和可选参数
所需参数 这些参数需要在配置文件 Harbor.cfg 中设置。
如果用户更新它们并运行 install.sh脚本重新安装 Harbour，
参数将生效。具体参数如下：
hostname：用于访问用户界面和 register 服务。它应该是目标机器的 IP 地址或完全合格域名（FQDN）（主机名+域名）
dns
http://www.baidu.com:80/
协议://主机名.二级域名.顶级域 根域: 端口/
www.baidu.com 完全合格域名 FQDN
例如 192.168.195.128 或 hub.kgc.cn。(不要使用 localhost 或 127.0.0.1 为主机名。）
ui_url_protocol：（http 或 https，默认为 http）用于访问 UI 和令牌/通知服务的协议。如果公证处于启用状态，则此参数必须为 https。
max_job_workers：镜像复制作业线程。即私有仓库进行并发
db_password：用于db_auth 的MySQL数据库root 用户的密码。（Harbour自带一个mysql数据库）
customize_crt：该属性可设置为打开或关闭，默认打开。打开此属性时，需要准备脚本创建私钥和根证书，用于生成/验证注册表令牌。
当由外部来源提供密钥和根证书时，将此属性设置为 off。
ssl_cert：SSL 证书的路径，仅当协议设置为 https（基于SSL证书） 时才应用。
ssl_cert_key：SSL 密钥的路径，仅当协议设置为 https 时才应用。
secretkey_path：用于在复制策略中加密或解密远程 register 密码的密钥路径。
可选参数
这些参数对于更新是可选的，即用户可以将其保留为默认值，并在启动 Harbor 后在 Web UI 上进行更新。
如果进入 Harbor.cfg，只会在第一次启动 Harbor 时生效，随后对这些参数 的更新，Harbor.cfg 将被忽略。
注意：如果选择通过UI设置这些参数，请确保在启动Harbour后立即执行此操作。具体来说，必须在注册或在 Harbor 中创建任何新用户之前设置所需的
auth_mode。当系统中有用户时（除了默认的 admin 用户），auth_mode 不能被修改。具体参数如下：
Email：Harbor需要该参数才能向用户发送“密码重置”电子邮件，并且只有在需要该功能时才需要。
请注意，在默认情况下SSL连接时没有启用。如果SMTP服务器需要SSL，但不支持STARTTLS，那么应该通过设置启用SSL email_ssl = TRUE。
harbour_admin_password：管理员的初始密码，只在Harbour第一次启动时生效。之后，此设置将被忽略，并且应 UI中设置管理员的密码。
请注意，默认的用户名/密码是 admin/Harbor12345。
auth_mode：使用的认证类型，默认情况下，它是 db_auth，即凭据存储在数据库中。对于LDAP身份验证，请将其设置为 ldap_auth。
self_registration：启用/禁用用户注册功能。禁用时，新用户只能由 Admin 用户创建，只有管理员用户可以在 Harbour中创建新用户。
注意：当 auth_mode 设置为 ldap_auth 时，自注册功能将始终处于禁用状态，并且该标志被忽略。
Token_expiration：由令牌服务创建的令牌的到期时间（分钟），默认为 30 分钟。
project_creation_restriction：用于控制哪些用户有权创建项目的标志。默认情况下， 每个人都可以创建一个项目。
如果将其值设置为“adminonly”，那么只有 admin 可以创建项目。
verify_remote_cert：打开或关闭，默认打开。此标志决定了当Harbor与远程 register 实例通信时是否验证 SSL/TLS 证书。
将此属性设置为 off 将绕过 SSL/TLS 验证，这在远程实例具有自签名或不可信证书时经常使用。
另外，默认情况下，Harbour 将镜像存储在本地文件系统上。在生产环境中，可以考虑 使用其他存储后端而不是本地文件系统，
如 S3、Openstack Swif（对象存储）、Ceph 等。但需要更新 common/templates/registry/config.yml 文件。打开网站，查看效果图
用户名：admin 密码：Harbor12345
输入进入之后的效果图（私有仓库，镜像仓库）
查看容器状态
[root@server1 harbor]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1e2939aa770b vmware/nginx-photon:1.11.13 "nginx -g 'daemon of…" 9 minutes ago Up 9 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:4443->4443/tcp nginx
bd17fdc772bd vmware/harbor-jobservice:v1.2.2 "/harbor/harbor_jobs…" 9 minutes ago Up 9 minutes harbor-jobservice
f8a3176d531a vmware/harbor-ui:v1.2.2 "/harbor/harbor_ui" 9 minutes ago Up 9 minutes harbor-ui
9365b9b7175b vmware/harbor-adminserver:v1.2.2 "/harbor/harbor_admi…" 9 minutes ago Up 9 minutes harbor-adminserver
2c8ed5239460 vmware/harbor-db:v1.2.2 "docker-entrypoint.s…" 9 minutes ago Up 9 minutes 3306/tcp harbor-db
309735b4ef5f vmware/registry:2.6.2-photon "/entrypoint.sh serv…" 9 minutes ago Up 9 minutes 5000/tcp registry
dbc6dc933b6b vmware/harbor-log:v1.2.2 "/bin/sh -c 'crond &…" 9 minutes ago Up 9 minutes 127.0.0.1:1514->514/tcp创建项目，并填写项目名称
点击添加
点击wang（项目），进入项目
登录
[root@server1 harbor]# cd
[root@server1 ~]# docker login -u admin -p Harbor12345 http://127.0.0.1
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
[root@server1 ~]# ls -a //.docker（隐藏文件）查看到有生成
[root@server1 ~]# cd .docker/
[root@server1 .docker]# ls
config.json
[root@server1 .docker]# vim config.json
{
"auths": {
"127.0.0.1": {
"auth": "YWRtaW46SGFyYm9yMTIzNDU（令牌）="
}
},
"HttpHeaders": {
"User-Agent": "Docker-Client/19.03.13 (linux)"
}
}
查看令牌并解码
[root@server1 .docker]# cat config.json | base64 -w 0
ewoJImF1dGhzIjogewoJCSIxMjcuMC4wLjEiOiB7CgkJCSJhdXRoIjogIllXUnRhVzQ2U0dGeVltOXlNVEl6TkRVPSIKCQl9Cgl9LAoJIkh0dHBIZWFkZXJzIjogewoJCSJVc2VyLUFnZW50IjogIkRvY2tlci1DbGllbnQvMTkuMDMuMTMgKGxpbnV4KSIKCX0KfQ==[root@server1 .docker]#
验证的令牌（登录到Harbor自动生成的）从官网下载镜像tomcat进行测试
回车
[root@server1 .docker]# docker pull tomcat
点击推送镜像，复制
粘贴并修改docker tag SOURCE_IMAGE[:TAG] 20.0.0.11/wang/IMAGE[:TAG]
修改并打标签
[root@server1 .docker]# docker tag tomcat:latest 20.0.0.11/wang/tomcat:v1
上传镜像至Harbor仓库//发现被拒绝
[root@server1 .docker]# docker tag tomcat:latest 20.0.0.11/wang/tomcat:v1
[root@server1 .docker]# docker push 20.0.0.11/wang/tomcat
The push refers to repository [20.0.0.11/wang/tomcat]
Get https://20.0.0.11/v2/: dial tcp 20.0.0.11:443: connect: connection refused上传镜像至Harbor仓库//上传本地
[root@server1 .docker]# docker tag tomcat:latest 127.0.0.1/wang/tomcat:v1
[root@server1 .docker]# docker push 127.0.0.1/wang/tomcat //此时可以上传成
功
此时，为什么上传20.0.0.11的ip上传失败
另外开启另一台服务器连接Harbor仓库，出现如下报错
[root@node ~]# docker login -u admin -p Harbor12345 http://20.0.0.11
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://20.0.0.11/v2/: dial tcp 20.0.0.11:443: connect: connection refused两个问题如何解决（以上问题都使用该方案）
[root@node ~]# vim /usr/lib/systemd/system/docker.service
添加--insecure-registry 20.0.0.11
14 ExecStart=/usr/bin/dockerd -H fd:// --insecure-registry 20.0.0.11 --containerd=/run/containerd/containerd.sock
[root@node ~]# systemctl restart docker //重启服务
Warning: docker.service changed on disk. Run 'systemctl daemon-reload' to reload units.
[root@node ~]# systemctl daemon-reload //重载，重启服务
[root@node ~]# systemctl restart docker[root@node ~]# docker login -u admin -p Harbor12345 http://20.0.0.11 //此时可以登录成功
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded另一端下载nginx
[root@node ~]# docker pull nginx
打标签上传Harbor仓库 （复制推荐镜像，标记镜像）
[root@node ~]# docker tag nginx:latest 20.0.0.11/wang/nginx:v1
[root@node ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
20.0.0.11/wang/nginx v1 bc9a0695f571 7 days ago 133MB
nginx latest bc9a0695f571 7 days ago 133MB
[root@node ~]# docker push 20.0.0.11/wang/nginx:v1 //上传镜像至Harbor仓库（私有仓库）
此时，有两个镜像生成
清空所有镜像，做在Harbor仓库做下载验证（私有仓库下载）
[root@node ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
复制pull命令做下载
[root@node ~]# docker images //镜像已下载
REPOSITORY TAG IMAGE ID CREATED SIZE
20.0.0.11/wang/nginx v1 bc9a0695f571 7 days ago 133MB
下载后出现统计其他用户进行管理
点击+用户
给wangtong用户附加权限，需要添加到项目当中
此时wangtong用户登录一样可以实现上传和下载
修改Harbor.cfg配置文件（关闭和开启Harbor仓库）
[root@server1 .docker]# cd /usr/local/harbor/ 在和docker-compose.yml路径相同的目录下进行
[root@server1 harbor]# ls
docker-compose.yml
[root@server1 harbor]# docker-compose down -v
[root@server1 harbor]# docker ps -a //此时容器被清空
[root@server1 harbor]# docker-compose up -d
此时仓库重新启动，我们使用wangtong用户进行登录退出登录
[root@node ~]# docker logout 20.0.0.11
Removing login credentials for 20.0.0.11
以wangtong账户进行登录
[root@node ~]# docker login -u wangtong -p Harbor12345 http://20.0.0.11
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded//查看 Docker-Compose 版本判断安装是否成功
cp docker-compose /usr/local/bin/
docker-compose -v
本文章为转载内容，我们尊重原作者对文章享有的著作权。如有内容错误或侵权问题，欢迎原作者联系我们进行内容更正或删除文章。
