首页 > 其他分享 >docker-compose 部署 harbor 镜像仓库

docker-compose 部署 harbor 镜像仓库

时间:2023-12-18 10:05:03浏览次数:44  
标签:compose harbor config common file docker configuration root

1、安装 docker(这个就不写了,可以看)
略......

2、安装 docker-compose

[root@master2 ~]# curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

[root@master2 ~]# chmod +x /usr/local/bin/docker-compose

3、下载 harbor-offline-installer-v1.7.5.tgz 安装包并解压

[root@master2 ~]# wget https://storage.googleapis.com/harbor-releases/release-1.7.0/harbor-offline-installer-v1.7.5.tgz
[root@master2 ~]# mkdir /data/cert

[root@master2 ~]# tar -zxf harbor-offline-installer-v1.7.5.tgz -C /data/

4、修改 harbor.cfg 配置文件

[root@master2 ~]# cat /data/harbor/harbor.cfg 
## Configuration file of Harbor

#This attribute is for migrator to detect the version of the .cfg file, DO NOT MODIFY!
_version = 1.7.0
#The IP address or hostname to access admin UI and registry service.
#DO NOT use localhost or 127.0.0.1, because Harbor needs to be accessed by external clients.
#DO NOT comment out this line, modify the value of "hostname" directly, or the installation will fail.
hostname = 192.168.200.4                    # 可以写主机名或者IP

#The protocol for accessing the UI and token/notification service, by default it is http.
#It can be set to https if ssl is enabled on nginx.
ui_url_protocol = https                     # 根据自己情况配置

#Maximum number of job workers in job service  
max_job_workers = 10 

#Determine whether or not to generate certificate for the registry's token.
#If the value is on, the prepare script creates new root cert and private key 
#for generating token to access the registry. If the value is off the default key/cert will be used.
#This flag also controls the creation of the notary signer's cert.
customize_crt = on

#The path of cert and key files for nginx, they are applied only the protocol is set to https
port: 443                                       # 端口不一样就添加
ssl_cert = /data/cert/server.crt                # 证书路径根据自己环境创建
ssl_cert_key = /data/cert/server.key            # 同上

#The path of secretkey storage
secretkey_path = /data

#Admiral's url, comment this attribute, or set its value to NA when Harbor is standalone
admiral_url = NA

#Log files are rotated log_rotate_count times before being removed. If count is 0, old versions are removed rather than rotated.
log_rotate_count = 50
#Log files are rotated only if they grow bigger than log_rotate_size bytes. If size is followed by k, the size is assumed to be in kilobytes. 
#If the M is used, the size is in megabytes, and if G is used, the size is in gigabytes. So size 100, size 100k, size 100M and size 100G 
#are all valid.
log_rotate_size = 200M

#Config http proxy for Clair, e.g. http://my.proxy.com:3128
#Clair doesn't need to connect to harbor internal components via http proxy.
http_proxy =
https_proxy =
no_proxy = 127.0.0.1,localhost,core,registry

#NOTES: The properties between BEGIN INITIAL PROPERTIES and END INITIAL PROPERTIES
#only take effect in the first boot, the subsequent changes of these properties 
#should be performed on web ui

#************************BEGIN INITIAL PROPERTIES************************

#Email account settings for sending out password resetting emails.

#Email server uses the given username and password to authenticate on TLS connections to host and act as identity.
#Identity left blank to act as username.
email_identity = 

email_server = smtp.mydomain.com
email_server_port = 25
email_username = [email protected]
email_password = abc
email_from = admin <[email protected]>
email_ssl = false
email_insecure = false

##The initial password of Harbor admin, only works for the first time when Harbor starts. 
#It has no effect after the first launch of Harbor.
#Change the admin password from UI after launching Harbor.
harbor_admin_password = Harbor12345                # 密码可以自己修改

##By default the auth mode is db_auth, i.e. the credentials are stored in a local database.
#Set it to ldap_auth if you want to verify a user's credentials against an LDAP server.
auth_mode = db_auth

#The url for an ldap endpoint.
ldap_url = ldaps://ldap.mydomain.com

#A user's DN who has the permission to search the LDAP/AD server. 
#If your LDAP/AD server does not support anonymous search, you should configure this DN and ldap_search_pwd.
#ldap_searchdn = uid=searchuser,ou=people,dc=mydomain,dc=com

#the password of the ldap_searchdn
#ldap_search_pwd = password

#The base DN from which to look up a user in LDAP/AD
ldap_basedn = ou=people,dc=mydomain,dc=com

#Search filter for LDAP/AD, make sure the syntax of the filter is correct.
#ldap_filter = (objectClass=person)

# The attribute used in a search to match a user, it could be uid, cn, email, sAMAccountName or other attributes depending on your LDAP/AD  
ldap_uid = uid 

#the scope to search for users, 0-LDAP_SCOPE_BASE, 1-LDAP_SCOPE_ONELEVEL, 2-LDAP_SCOPE_SUBTREE
ldap_scope = 2 

#Timeout (in seconds)  when connecting to an LDAP Server. The default value (and most reasonable) is 5 seconds.
ldap_timeout = 5

#Verify certificate from LDAP server
ldap_verify_cert = true

#The base dn from which to lookup a group in LDAP/AD
ldap_group_basedn = ou=group,dc=mydomain,dc=com

#filter to search LDAP/AD group
ldap_group_filter = objectclass=group

#The attribute used to name a LDAP/AD group, it could be cn, name
ldap_group_gid = cn

#The scope to search for ldap groups. 0-LDAP_SCOPE_BASE, 1-LDAP_SCOPE_ONELEVEL, 2-LDAP_SCOPE_SUBTREE
ldap_group_scope = 2

#Turn on or off the self-registration feature
self_registration = on

#The expiration time (in minute) of token created by token service, default is 30 minutes
token_expiration = 30

#The flag to control what users have permission to create projects
#The default value "everyone" allows everyone to creates a project. 
#Set to "adminonly" so that only admin user can create project.
project_creation_restriction = everyone

#************************END INITIAL PROPERTIES************************

#######Harbor DB configuration section#######

#The address of the Harbor database. Only need to change when using external db.
db_host = postgresql

#The password for the root user of Harbor DB. Change this before any production use.
db_password = root123

#The port of Harbor database host
db_port = 5432

#The user name of Harbor database
db_user = postgres

##### End of Harbor DB configuration#######

##########Redis server configuration.############

#Redis connection address
redis_host = redis

#Redis connection port
redis_port = 6379

#Redis connection password
redis_password = 

#Redis connection db index
#db_index 1,2,3 is for registry, jobservice and chartmuseum. 
#db_index 0 is for UI, it's unchangeable
redis_db_index = 1,2,3

########## End of Redis server configuration ############

##########Clair DB configuration############

#Clair DB host address. Only change it when using an exteral DB.
clair_db_host = postgresql
#The password of the Clair's postgres database. Only effective when Harbor is deployed with Clair.
#Please update it before deployment. Subsequent update will cause Clair's API server and Harbor unable to access Clair's database.
clair_db_password = root123
#Clair DB connect port
clair_db_port = 5432
#Clair DB username
clair_db_username = postgres
#Clair default database
clair_db = postgres

#The interval of clair updaters, the unit is hour, set to 0 to disable the updaters.
clair_updaters_interval = 12

##########End of Clair DB configuration############

#The following attributes only need to be set when auth mode is uaa_auth
uaa_endpoint = uaa.mydomain.org
uaa_clientid = id
uaa_clientsecret = secret
uaa_verify_cert = true
uaa_ca_cert = /path/to/ca.pem


### Harbor Storage settings ###
#Please be aware that the following storage settings will be applied to both docker registry and helm chart repository.
#registry_storage_provider can be: filesystem, s3, gcs, azure, etc.
registry_storage_provider_name = filesystem
#registry_storage_provider_config is a comma separated "key: value" pairs, e.g. "key1: value, key2: value2".
#To avoid duplicated configurations, both docker registry and chart repository follow the same storage configuration specifications of docker registry.
#Refer to https://docs.docker.com/registry/configuration/#storage for all available configuration.
registry_storage_provider_config =
#registry_custom_ca_bundle is the path to the custom root ca certificate, which will be injected into the truststore
#of registry's and chart repository's containers.  This is usually needed when the user hosts a internal storage with self signed certificate.
registry_custom_ca_bundle = 

#If reload_config=true, all settings which present in harbor.cfg take effect after prepare and restart harbor, it overwrites exsiting settings.
#reload_config=true
#Regular expression to match skipped environment variables
#skip_reload_env_pattern=(^EMAIL.*)|(^LDAP.*)

5、生成CA证书
1> 创建key文件

[root@master2 cert]# openssl genrsa -out ca.key 4096
 Generating RSA private key, 4096 bit long modulus
 ............++
 .........................++
 e is 65537 (0x10001)

2> 生成证书

[root@master2 cert]# openssl req -x509 -new -nodes -sha512 -days 3650  -subj "/CN=192.168.200.4"  -key ca.key  -out ca.crt

[root@k8s_master2 harbor]# ll /data/cert/
total 28
-rw-r--r-- 1 root root 1797 Mar 24 05:37 ca.crt
-rw-r--r-- 1 root root 3243 Mar 24 05:37 ca.key

6、生成服务器证书
1> 创建私钥

[root@master2 cert]# openssl genrsa -out server.key 4096
 Generating RSA private key, 4096 bit long modulus
 ........................................................................................................................................................++
 .............................................................................++
 e is 65537 (0x10001)

2> 生成证书签名请求

[root@master2 cert]# openssl req  -new -sha512  -subj "/CN=192.168.200.4"  -key server.key  -out server.csr

3> 查看证书

[root@master2 ~]# ll /data/cert/
total 28
-rw-r--r-- 1 root root 1797 Mar 24 05:37 ca.crt
-rw-r--r-- 1 root root 3243 Mar 24 05:37 ca.key
-rw-r--r-- 1 root root 1590 Mar 24 05:38 server.csr
-rw-r--r-- 1 root root 3247 Mar 24 05:38 server.key

7、生成harbor仓库主机的证书
1> 创建 v3.ext 文件

[root@master2 cert]# cat v3.ext 
authorityKeyIdentifier=keyid,issuer
basicConstraints=CA:FALSE
keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth 
subjectAltName = @alt_names

[alt_names]
DNS=192.168.200.4

2> 生成harbor仓库主机的证书

[root@master2 cert]# openssl x509 -req -sha512 -days 3650 -extfile v3.ext -CA ca.crt -CAkey ca.key -CAcreateserial -in server.csr -out server.crt
 Signature ok
 subject=/CN=harbor23.com
 Getting CA Private Key

3> 再次查看生成的所有证书

[root@master2 ~]# ll /data/cert/
total 28
-rw-r--r-- 1 root root 1797 Mar 24 05:37 ca.crt
-rw-r--r-- 1 root root 3243 Mar 24 05:37 ca.key
-rw-r--r-- 1 root root   17 Mar 24 05:40 ca.srl
-rw-r--r-- 1 root root 1834 Mar 24 05:40 server.crt
-rw-r--r-- 1 root root 1590 Mar 24 05:38 server.csr
-rw-r--r-- 1 root root 3247 Mar 24 05:38 server.key
-rw-r--r-- 1 root root  231 Mar 24 05:39 v3.ext

8、为docker配置harbor认证

mkdir /etc/docker/certs

scp /data/cert/server.crt [email protected]:/etc/docker/certs

注意:harbor.cfg 配置文件中 server.crt和server.key在哪个路径下就要把这两个证书移动到哪个路径下,必需要一致。

9、安装

[root@master2 harbor]# ./prepare 
Clearing the configuration file: ./common/config/adminserver/env
Clearing the configuration file: ./common/config/core/env
Clearing the configuration file: ./common/config/core/app.conf
Clearing the configuration file: ./common/config/core/private_key.pem
Clearing the configuration file: ./common/config/db/env
Clearing the configuration file: ./common/config/jobservice/env
Clearing the configuration file: ./common/config/jobservice/config.yml
Clearing the configuration file: ./common/config/registry/config.yml
Clearing the configuration file: ./common/config/registry/root.crt
Clearing the configuration file: ./common/config/registryctl/env
Clearing the configuration file: ./common/config/registryctl/config.yml
Clearing the configuration file: ./common/config/nginx/nginx.conf
Clearing the configuration file: ./common/config/log/logrotate.conf
loaded secret from file: /data/secretkey
Generated configuration file: ./common/config/nginx/nginx.conf
Generated configuration file: ./common/config/adminserver/env
Generated configuration file: ./common/config/core/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/config.yml
Generated configuration file: ./common/config/log/logrotate.conf
Generated configuration file: ./common/config/registryctl/env
Generated configuration file: ./common/config/core/app.conf
Generated certificate, key file: ./common/config/core/private_key.pem, cert file: ./common/config/registry/root.crt
The configuration files are ready, please use docker-compose to start the service.
[root@master2 harbor]# ./install.sh 

[Step 0]: checking installation environment ...

Note: docker version: 19.03.15

Note: docker-compose version: 1.29.2

[Step 1]: loading Harbor images ...
Loaded image: goharbor/harbor-adminserver:v1.7.5
Loaded image: goharbor/harbor-portal:v1.7.5
Loaded image: goharbor/harbor-db:v1.7.5
Loaded image: goharbor/registry-photon:v2.6.2-v1.7.5
Loaded image: goharbor/harbor-migrator:v1.7.5
Loaded image: goharbor/harbor-core:v1.7.5
Loaded image: goharbor/harbor-log:v1.7.5
Loaded image: goharbor/redis-photon:v1.7.5
Loaded image: goharbor/nginx-photon:v1.7.5
Loaded image: goharbor/harbor-registryctl:v1.7.5
Loaded image: goharbor/chartmuseum-photon:v0.8.1-v1.7.5
Loaded image: goharbor/harbor-jobservice:v1.7.5
Loaded image: goharbor/notary-server-photon:v0.6.1-v1.7.5
Loaded image: goharbor/notary-signer-photon:v0.6.1-v1.7.5
Loaded image: goharbor/clair-photon:v2.0.8-v1.7.5


[Step 2]: preparing environment ...
Clearing the configuration file: ./common/config/adminserver/env
Clearing the configuration file: ./common/config/core/env
Clearing the configuration file: ./common/config/core/app.conf
Clearing the configuration file: ./common/config/core/private_key.pem
Clearing the configuration file: ./common/config/db/env
Clearing the configuration file: ./common/config/jobservice/env
Clearing the configuration file: ./common/config/jobservice/config.yml
Clearing the configuration file: ./common/config/registry/config.yml
Clearing the configuration file: ./common/config/registry/root.crt
Clearing the configuration file: ./common/config/registryctl/env
Clearing the configuration file: ./common/config/registryctl/config.yml
Clearing the configuration file: ./common/config/nginx/nginx.conf
Clearing the configuration file: ./common/config/log/logrotate.conf
loaded secret from file: /data/secretkey
Generated configuration file: ./common/config/nginx/nginx.conf
Generated configuration file: ./common/config/adminserver/env
Generated configuration file: ./common/config/core/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/config.yml
Generated configuration file: ./common/config/log/logrotate.conf
Generated configuration file: ./common/config/registryctl/env
Generated configuration file: ./common/config/core/app.conf
Generated certificate, key file: ./common/config/core/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 ...

Note: stopping existing Harbor instance ...
Stopping nginx              ... done
Stopping harbor-portal      ... done
Stopping harbor-jobservice  ... done
Stopping harbor-core        ... done
Stopping registry           ... done
Stopping harbor-adminserver ... done
Stopping redis              ... done
Stopping harbor-db          ... done
Stopping registryctl        ... done
Stopping harbor-log         ... done
Removing nginx              ... done
Removing harbor-portal      ... done
Removing harbor-jobservice  ... done
Removing harbor-core        ... done
Removing registry           ... done
Removing harbor-adminserver ... done
Removing redis              ... done
Removing harbor-db          ... done
Removing registryctl        ... done
Removing harbor-log         ... done
Removing network harbor_harbor


[Step 4]: starting Harbor ...
Creating network "harbor_harbor" with the default driver
Creating harbor-log ... done
Creating redis              ... done
Creating registryctl        ... done
Creating registry           ... done
Creating harbor-adminserver ... done
Creating harbor-db          ... done
Creating harbor-core        ... done
Creating harbor-portal      ... 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://192.168.200.4. 
For more details, please visit https://github.com/goharbor/harbor .

10、访问 web

docker-compose 部署 harbor 镜像仓库_Redis

11、创建项目

docker-compose 部署 harbor 镜像仓库_docker_02

12、在另一台服务器登录 harbor 仓库
1> 修改另一台服务器 daemon.json 配置文件

[root@node1 data]# cat /etc/docker/daemon.json 
{
  "data-root": "/data/docker",
  "registry-mirrors":["https://docker.mirrors.ustc.edu.cn"],
  "insecure-registries": ["192.168.200.4"],                 # 添加这一行(里面的ip是本机的hostname)
  "log-opts": {
    "max-size": "5m",
    "max-file":"3"
  },
  "exec-opts": ["native.cgroupdriver=systemd"]
}

2> 重启 docker

systemctl restart docker

3> 登录 harbor

[root@node1 ~]# docker login 192.168.200.4 或者 docker login https://192.168.200.4
Username: admin
Password: 
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

注意:如果不修改 daemon.json 直接登录 harbor 会提示以下错误

[root@node1 ~]# docker login 192.168.200.4
Username: admin
Password: 
Error response from daemon: Get https://192.168.200.4/v2/: dial tcp 192.168.200.4:443: connect: connection refused

13、上传镜像到 harbor

[root@node1 ~]# docker images 
REPOSITORY                                                         TAG                 IMAGE ID            CREATED             SIZE
nginx                                                              latest              605c77e624dd        2 months ago        141MB

[root@node1 ~]# docker tag nginx 192.168.200.4/k8s_images/nginx:latest

[root@node1 ~]# docker images 
REPOSITORY                                                         TAG                 IMAGE ID            CREATED             SIZE
192.168.200.4/k8s_images/nginx                                     latest              605c77e624dd        2 months ago        141MB
nginx                                                              latest              605c77e624dd        2 months ago        141MB


[root@node1 ~]# docker push 192.168.200.4/k8s_images/nginx
The push refers to repository [192.168.200.4/k8s_images/nginx]
d874fd2bc83b: Pushed 
32ce5f6a5106: Pushed 
f1db227348d0: Pushed 
b8d6e692a25e: Pushed 
e379e8aedd4d: Pushed 
2edcec3590a4: Pushed 
latest: digest: sha256:ee89b00528ff4f02f2405e4ee221743ebc3f8e8dd0bfd5c4c20a2fa2aaa7ede3 size: 1570

14、查看已上传的镜像

docker-compose 部署 harbor 镜像仓库_docker_03

标签:compose,harbor,config,common,file,docker,configuration,root
From: https://blog.51cto.com/u_14620403/8868205

相关文章

  • pytorch的docker镜像
    安装docker环境sudoapt-getupdatesudoapt-getinstall-ydocker.iosudosystemctlenabledockerdocker版本查看sudodockerversionsudodockerinfo查看镜像sudodockerimagessudodockerimagels查看容器sudodockerpssudodockerps-a导入镜像文件s......
  • Centos7的宝塔系统上用Docker安装Openwrt
    Docker安装Openwrt,我是按照林中静月下仙的博客做的 主机是Dell的E7250I5-5300U先安装Centos7.9,然后使用手机做热点安装了宝塔系统,大约用了五六个小时。然后在宝塔系统的软件商店搜索,安装 设置加速url 拉取openwrt镜像【registry.cn-shanghai.aliyuncs.com/suling/......
  • docker可视化操作
    云原生之部署Docker可视化管理工具docker.ui原创 江湖有缘 运维技术学习 2023-12-1518:10 发表于湖北一、docker.ui介绍1.docker.ui简介DockerUI是一个易用且轻量化的Docker管理工具,透过Web界面的操作,更方便对于Docker指令不熟悉的用户更容易操作Docker。......
  • Docker Compose 快速搭建 Redis 单机版
    Redis是非常流行的缓存中间件,其具有功能强大和部署简单的优势,我们在CentOS上使用yum就能够在线安装Redis。之所以要介绍使用Docker进行容器化部署Redis,主要原因是当前容器化部署是主流,而且能够保障服务器文件系统的整洁。本篇博客主要介绍如何使用docker-compose快速......
  • docker从0安装Jenkins
    docker从0安装JenkinsUbuntu初始化sudoapt-getinstallopenssh-serversudovim/etc/ssh/sshd_config设置静态IPcd/etc/netplan···network:version:2renderer:NetworkManagerethernets:ens33:#网卡名称dhcp4:no#关闭dhcp......
  • DOCKER20231217: 容器引擎Docker
       1.1Docker简介 1.1.1什么是Docker?一种轻量级的操作系统虚拟化技术,基于Go语言实现的开源容器项目,诞生于2013年,最初发起者是dotCloud公司(现DockerInc)Docker容器化虚拟技术vs传统虚拟机技术特性容器虚拟机启动秒级分钟级硬盘使用一般为MB一般为G......
  • 使用Docker自定义配置部署RustDesk Server
    “RustDesk是一款可以平替TeamViewer的开源软件,旨在提供安全便捷的自建方案。”这是RustDesk官网对自己的描述。作为一款使用Rust语言开发的开源软件,在为数不多的Rust开发者和数量庞大的Rust学习者中还是有相当的知名度的,并且商业化的RustDeskPro也是如火如荼。开始docker......
  • docker制作镜像太大如何处理
    1.在编写Dockerfile文件时,可以使用 .dockerignore 文件来指定需要从上下文中排除的文件和目录。可以将不需要包含在镜像中的路径添加到 .dockerignore 文件中,然后在通过 2.dockerbuild 命令构建镜像时,Docker 会自动排除这些路径。......
  • 4-Docker命令之docker stop
    1.dockerstop介绍dockerstop命令是用来停止一个运行中的docker容器。2.dockerstop用法dockerstop[参数]container[container......][root@centos79~]#dockerstop--helpUsage:dockerstop[OPTIONS]CONTAINER[CONTAINER...]Stoponeormorerunningcontainers......
  • Docker 部署数据可视化 Superset 3.0.0 深度汉化并配置元数据存储为 Postgres
    Superset官方提供的Docker镜像在3.0.0版本下不能做到开箱即用,需要一些设置拉取原始镜像dockerpullapache/superset:3.0.0配置superset_config.pysuperset_config.py会覆盖掉config.py里的变量,无需配置config.py创建一个superset_config.py文件添加以下内容SECRET......