最新国产好看的视频,伊人天堂AV在线,国产Aaaaaa视频,蜜臀视频在线观看一区,人妻av色图,密臀久久久精品影片,青青视频免费观看毛片,久草在线观看视,国产三级精品色情在线

harbor倉庫搭建全過程(配置https)

 更新時間:2025年09月22日 10:01:59   作者:九制橘皮茶  
需安裝Docker及Docker Compose,Harbor版本需匹配,因密碼加密算法升級至SHA1,需配置HTTPS以避免登錄錯誤,步驟包括生成CA證書、修改配置、啟動倉庫、訪問地址及數(shù)據(jù)庫調(diào)整加密算法,最后設(shè)置開機自啟

1. 環(huán)境準(zhǔn)備

需要提前安裝docker和docker-compose,harbor倉庫版本越新,對應(yīng)的docker和docker-compose版本越新。

主機IP192.168.48.19
docker版本28.3.3
docker-compose版本2.39.1

2. 配置https的原因

為什么harbor要配置https?

如果不配置https的話會報下面的錯:用戶名或者密碼不正確。

原因:

harbor修改了密碼的加密算法,舊算法是sha256,新算法sha1,不巧的是這個算法http目前不支持,所以改為https。

HTTP主要使用以下加密算法:

TLS/SSL加密(HTTPS)

  • 對稱加密:AES、ChaCha20、3DES等
  • 非對稱加密:RSA、ECC、DSA等
  • 密鑰交換:ECDHE、DHE、RSA等
  • 哈希算法:SHA256、SHA384、SHA512等(現(xiàn)代TLS已棄用SHA1)

HTTP摘要認證

  • 使用MD5、SHA256等哈希算法
  • 但不直接使用SHA1

3. 生成ca證書

mkdir -p /var/harbor/cert && cd  /var/harbor/cert
openssl genrsa -out ca.key 4096
openssl req -x509 -new -nodes -sha512 -days 3650 -subj "/C=CN/ST=Beijing/L=Beijing/O=example/OU=Personal/CN=192.168.48.19" -key ca.key -out ca.crt
openssl genrsa -out 192.168.48.19.key 4096
openssl req -sha512 -new     -subj "/C=CN/ST=Beijing/L=Beijing/O=example/OU=Personal/CN=192.168.48.19"     -key 192.168.48.19.key     -out 192.168.48.19.csr
cat > v3.ext <<-EOF
authorityKeyIdentifier=keyid,issuer
basicConstraints=CA:FALSE
keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth
subjectAltName = @alt_names
?
[alt_names]
DNS.1=192.168.48.19
DNS.2=127.0.0.1
IP.1=192.168.48.19
EOF
openssl x509 -req -sha512 -days 3650     -extfile v3.ext     -CA ca.crt -CAkey 

4. 搭建harbor倉庫

wget https://github.com/goharbor/harbor/releases/download/v2.12.3/harbor-offline-installer-v2.12.3.tgz
tar -zxf harbor-offline-installer-v2.12.3.tgz
cp harbor.yml.tmpl harbor.yml

更改配置文件,下面是我的配置文件,IP根據(jù)自己的環(huán)境配置

# Configuration file of Harbor
?
# 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.
hostname: 192.168.48.19
?
# http related config
http:
  # port for http, default is 80. If https enabled, this port will redirect to https port
  port: 80
?
# https related config
https:
  # https port for harbor, default is 443
  port: 443
  # The path of cert and key files for nginx
  certificate: /var/harbor/cert/192.168.48.19.crt
  private_key: /var/harbor/cert/192.168.48.19.key
  # enable strong ssl ciphers (default: false)
  # strong_ssl_ciphers: false
?
# # Harbor will set ipv4 enabled only by default if this block is not configured
# # Otherwise, please uncomment this block to configure your own ip_family stacks
# ip_family:
#   # ipv6Enabled set to true if ipv6 is enabled in docker network, currently it affected the nginx related component
#   ipv6:
#     enabled: false
#   # ipv4Enabled set to true by default, currently it affected the nginx related component
#   ipv4:
#     enabled: true
?
# # Uncomment following will enable tls communication between all harbor components
# internal_tls:
#   # set enabled to true means internal tls is enabled
#   enabled: true
#   # put your cert and key files on dir
#   dir: /etc/harbor/tls/internal
?
?
# Uncomment external_url if you want to enable external proxy
# And when it enabled the hostname will no longer used
# external_url: https://reg.mydomain.com:8433
?
# The initial password of Harbor admin
# It only works in first time to install harbor
# Remember Change the admin password from UI after launching Harbor.
harbor_admin_password: Harbor12345
?
# Harbor DB configuration
database:
  # The password for the user('postgres' by default) of Harbor DB. Change this before any production use.
  password: root123
  # The maximum number of connections in the idle connection pool. If it <=0, no idle connections are retained.
  max_idle_conns: 100
  # The maximum number of open connections to the database. If it <= 0, then there is no limit on the number of open connections.
  # Note: the default number of connections is 1024 for postgres of harbor.
  max_open_conns: 900
  # The maximum amount of time a connection may be reused. Expired connections may be closed lazily before reuse. If it <= 0, connections are not closed due to a connection's age.
  # The value is a duration string. A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units are "ns", "us" (or "μs"), "ms", "s", "m", "h".
  conn_max_lifetime: 5m
  # The maximum amount of time a connection may be idle. Expired connections may be closed lazily before reuse. If it <= 0, connections are not closed due to a connection's idle time.
  # The value is a duration string. A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units are "ns", "us" (or "μs"), "ms", "s", "m", "h".
  conn_max_idle_time: 0
?
# The default data volume
data_volume: /data/harbor
?
# Harbor Storage settings by default is using /data dir on local filesystem
# Uncomment storage_service setting If you want to using external storage
# storage_service:
#   # ca_bundle is the path to the custom root ca certificate, which will be injected into the truststore
#   # of registry's containers.  This is usually needed when the user hosts a internal storage with self signed certificate.
#   ca_bundle:
?
#   # storage backend, default is filesystem, options include filesystem, azure, gcs, s3, swift and oss
#   # for more info about this configuration please refer https://distribution.github.io/distribution/about/configuration/
#   # and https://distribution.github.io/distribution/storage-drivers/
#   filesystem:
#     maxthreads: 100
#   # set disable to true when you want to disable registry redirect
#   redirect:
#     disable: false
?
# Trivy configuration
#
# Trivy DB contains vulnerability information from NVD, Red Hat, and many other upstream vulnerability databases.
# It is downloaded by Trivy from the GitHub release page https://github.com/aquasecurity/trivy-db/releases and cached
# in the local file system. In addition, the database contains the update timestamp so Trivy can detect whether it
# should download a newer version from the Internet or use the cached one. Currently, the database is updated every
# 12 hours and published as a new release to GitHub.
trivy:
  # ignoreUnfixed The flag to display only fixed vulnerabilities
  ignore_unfixed: false
  # skipUpdate The flag to enable or disable Trivy DB downloads from GitHub
  #
  # You might want to enable this flag in test or CI/CD environments to avoid GitHub rate limiting issues.
  # If the flag is enabled you have to download the `trivy-offline.tar.gz` archive manually, extract `trivy.db` and
  # `metadata.json` files and mount them in the `/home/scanner/.cache/trivy/db` path.
  skip_update: false
  #
  # skipJavaDBUpdate If the flag is enabled you have to manually download the `trivy-java.db` file and mount it in the
  # `/home/scanner/.cache/trivy/java-db/trivy-java.db` path
  skip_java_db_update: false
  #
  # The offline_scan option prevents Trivy from sending API requests to identify dependencies.
  # Scanning JAR files and pom.xml may require Internet access for better detection, but this option tries to avoid it.
  # For example, the offline mode will not try to resolve transitive dependencies in pom.xml when the dependency doesn't
  # exist in the local repositories. It means a number of detected vulnerabilities might be fewer in offline mode.
  # It would work if all the dependencies are in local.
  # This option doesn't affect DB download. You need to specify "skip-update" as well as "offline-scan" in an air-gapped environment.
  offline_scan: false
  #
  # Comma-separated list of what security issues to detect. Possible values are `vuln`, `config` and `secret`. Defaults to `vuln`.
  security_check: vuln
  #
  # insecure The flag to skip verifying registry certificate
  insecure: false
  #
  # timeout The duration to wait for scan completion.
  # There is upper bound of 30 minutes defined in scan job. So if this `timeout` is larger than 30m0s, it will also timeout at 30m0s.
  timeout: 5m0s
  #
  # github_token The GitHub access token to download Trivy DB
  #
  # Anonymous downloads from GitHub are subject to the limit of 60 requests per hour. Normally such rate limit is enough
  # for production operations. If, for any reason, it's not enough, you could increase the rate limit to 5000
  # requests per hour by specifying the GitHub access token. For more details on GitHub rate limiting please consult
  # https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting
  #
  # You can create a GitHub token by following the instructions in
  # https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
  #
  # github_token: xxx
?
jobservice:
  # Maximum number of job workers in job service
  max_job_workers: 10
  # The jobLoggers backend name, only support "STD_OUTPUT", "FILE" and/or "DB"
  job_loggers:
    - STD_OUTPUT
    - FILE
    # - DB
  # The jobLogger sweeper duration (ignored if `jobLogger` is `stdout`)
  logger_sweeper_duration: 1 #days
?
notification:
  # Maximum retry count for webhook job
  webhook_job_max_retry: 3
  # HTTP client timeout for webhook job
  webhook_job_http_client_timeout: 3 #seconds
?
# Log configurations
log:
  # options are debug, info, warning, error, fatal
  level: info
  # configs for logs in local storage
  local:
    # Log files are rotated log_rotate_count times before being removed. If count is 0, old versions are removed rather than rotated.
    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.
    rotate_size: 200M
    # The directory on your host that store log
    location: /var/log/harbor
?
  # Uncomment following lines to enable external syslog endpoint.
  # external_endpoint:
  #   # protocol used to transmit log to external endpoint, options is tcp or udp
  #   protocol: tcp
  #   # The host of external endpoint
  #   host: localhost
  #   # Port of external endpoint
  #   port: 5140
?
#This attribute is for migrator to detect the version of the .cfg file, DO NOT MODIFY!
_version: 2.12.0
?
# Uncomment external_database if using external database.
# external_database:
#   harbor:
#     host: harbor_db_host
#     port: harbor_db_port
#     db_name: harbor_db_name
#     username: harbor_db_username
#     password: harbor_db_password
#     ssl_mode: disable
#     max_idle_conns: 2
#     max_open_conns: 0
?
# Uncomment redis if need to customize redis db
# redis:
#   # db_index 0 is for core, it's unchangeable
#   # registry_db_index: 1
#   # jobservice_db_index: 2
#   # trivy_db_index: 5
#   # it's optional, the db for harbor business misc, by default is 0, uncomment it if you want to change it.
#   # harbor_db_index: 6
#   # it's optional, the db for harbor cache layer, by default is 0, uncomment it if you want to change it.
#   # cache_layer_db_index: 7
?
# Uncomment external_redis if using external Redis server
# external_redis:
#   # support redis, redis+sentinel
#   # host for redis: <host_redis>:<port_redis>
#   # host for redis+sentinel:
#   #  <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
#   host: redis:6379
#   password: 
#   # Redis AUTH command was extended in Redis 6, it is possible to use it in the two-arguments AUTH <username> <password> form.
#   # there's a known issue when using external redis username ref:https://github.com/goharbor/harbor/issues/18892
#   # if you care about the image pull/push performance, please refer to this https://github.com/goharbor/harbor/wiki/Harbor-FAQs#external-redis-username-password-usage
#   # username:
#   # sentinel_master_set must be set to support redis+sentinel
#   #sentinel_master_set:
#   # db_index 0 is for core, it's unchangeable
#   registry_db_index: 1
#   jobservice_db_index: 2
#   trivy_db_index: 5
#   idle_timeout_seconds: 30
#   # it's optional, the db for harbor business misc, by default is 0, uncomment it if you want to change it.
#   # harbor_db_index: 6
#   # it's optional, the db for harbor cache layer, by default is 0, uncomment it if you want to change it.
#   # cache_layer_db_index: 7
?
# Uncomment uaa for trusting the certificate of uaa instance that is hosted via self-signed cert.
# uaa:
#   ca_file: /path/to/ca
?
# Global proxy
# Config http proxy for components, e.g. http://my.proxy.com:3128
# Components doesn't need to connect to each others via http proxy.
# Remove component from `components` array if want disable proxy
# for it. If you want use proxy for replication, MUST enable proxy
# for core and jobservice, and set `http_proxy` and `https_proxy`.
# Add domain to the `no_proxy` field, when you want disable proxy
# for some special registry.
proxy:
  http_proxy:
  https_proxy:
  no_proxy:
  components:
    - core
    - jobservice
    - trivy
?
# metric:
#   enabled: false
#   port: 9090
#   path: /metrics
?
# Trace related config
# only can enable one trace provider(jaeger or otel) at the same time,
# and when using jaeger as provider, can only enable it with agent mode or collector mode.
# if using jaeger collector mode, uncomment endpoint and uncomment username, password if needed
# if using jaeger agetn mode uncomment agent_host and agent_port
# trace:
#   enabled: true
#   # set sample_rate to 1 if you wanna sampling 100% of trace data; set 0.5 if you wanna sampling 50% of trace data, and so forth
#   sample_rate: 1
#   # # namespace used to differentiate different harbor services
#   # namespace:
#   # # attributes is a key value dict contains user defined attributes used to initialize trace provider
#   # attributes:
#   #   application: harbor
#   # # jaeger should be 1.26 or newer.
#   # jaeger:
#   #   endpoint: http://hostname:14268/api/traces
#   #   username:
#   #   password:
#   #   agent_host: hostname
#   #   # export trace data by jaeger.thrift in compact mode
#   #   agent_port: 6831
#   # otel:
#   #   endpoint: hostname:4318
#   #   url_path: /v1/traces
#   #   compression: false
#   #   insecure: true
#   #   # timeout is in seconds
#   #   timeout: 10
?
# Enable purge _upload directories
upload_purging:
  enabled: true
  # remove files in _upload directories which exist for a period of time, default is one week.
  age: 168h
  # the interval of the purge operations
  interval: 24h
  dryrun: false
?
# Cache layer configurations
# If this feature enabled, harbor will cache the resource
# `project/project_metadata/repository/artifact/manifest` in the redis
# which can especially help to improve the performance of high concurrent
# manifest pulling.
# NOTICE
# If you are deploying Harbor in HA mode, make sure that all the harbor
# instances have the same behaviour, all with caching enabled or disabled,
# otherwise it can lead to potential data inconsistency.
cache:
  # not enabled by default
  enabled: false
  # keep cache for one day by default
  expire_hours: 24
?
# Harbor core configurations
# Uncomment to enable the following harbor core related configuration items.
# core:
#   # The provider for updating project quota(usage), there are 2 options, redis or db,
#   # by default is implemented by db but you can switch the updation via redis which
#   # can improve the performance of high concurrent pushing to the same project,
#   # and reduce the database connections spike and occupies.
#   # By redis will bring up some delay for quota usage updation for display, so only
#   # suggest switch provider to redis if you were ran into the db connections spike around
#   # the scenario of high concurrent pushing to same project, no improvement for other scenes.
#   quota_update_provider: redis # Or db

?啟動harbor倉庫

./install.sh

成功輸出:

 ? Network harbor_harbor        Created                                                                                      0.0s 
 ? Container harbor-log         Started                                                                                      0.2s 
 ? Container redis              Started                                                                                      0.8s 
 ? Container registryctl        Started                                                                                      0.5s 
 ? Container harbor-db          Started                                                                                      0.5s 
 ? Container registry           Started                                                                                      0.8s 
 ? Container harbor-portal      Started                                                                                      0.8s 
 ? Container harbor-core        Started                                                                                      0.9s 
 ? Container harbor-jobservice  Started                                                                                      1.1s 
 ? Container nginx              Started                                                                                      1.1s 
? ----Harbor has been installed and started successfully.----

5. 訪問harbor

harbor地址:192.192.48.1

6. 修改加密算法

如果還是顯示密碼錯誤,那就到數(shù)據(jù)庫里面改加密算法

[root@database harbor]# docker ps | grep  db
349bac5a56c4   goharbor/harbor-db:v2.12.3            "/docker-entrypoint.…"   5 minutes ago   Up 5 minutes (healthy)                                                                                        harbor-db
?
[root@database harbor]# docker exec -it 349bac5a56c4 /bin/bash
postgres [ / ]$ psql -d postgres
psql (15.12)
Type "help" for help.
?
postgres=# \c registry
You are now connected to database "registry" as user "postgres".
?
registry=# select * from harbor_user;    # 查看用戶表可以看到相關(guān)信息
?
# 將harbor_user表中的admin用戶的加密算法改為sha1,密碼改為Harbor12345
registry=# update harbor_user set password='a71a7d0df981a61cbb53a97ed8d78f3e', salt='ah3fdh5b7yxepalg9z45bu8zb36sszmr', password_version='sha1' where username='
admin';

然后重啟harbor就可以正常登錄了。

#到harbor目錄下
docker-compose down
docker-compose up -d

7. 配置開機自啟

cat > /usr/lib/systemd/system/harbor.service <<
[Unit]
Description=Harbor service with docker-compose
Requires=docker.service
After=docker.service
[Service]
Restart=always
RemainAfterExit=yes
StandardError=null
StandardOutput=null
WorkingDirectory=/root/harbor/harbor
ExecStartPre=/usr/local/bin/docker-compose -f /root/harbor/harbor/docker-compose.yml down
ExecStart=/usr/local/bin/docker-compose -f /root/harbor/harbor/docker-compose.yml up -d
ExecStop=/usr/local/bin/docker-compose -f /root/harbor/harbor/docker-compose.yml down
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl start harbor
systemctl enable harbor

總結(jié)

以上為個人經(jīng)驗,希望能給大家一個參考,也希望大家多多支持腳本之家。

相關(guān)文章

  • 運行中的docker容器端口映射如何修改詳解

    運行中的docker容器端口映射如何修改詳解

    這篇文章主要給大家介紹了關(guān)于運行中的docker容器端口映射如何修改的相關(guān)資料,文中通過示例代碼介紹的非常詳細,對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友們下面隨著小編來一起學(xué)習(xí)學(xué)習(xí)吧
    2021-01-01
  • Docker與docker-compose中volume參數(shù)的使用方式

    Docker與docker-compose中volume參數(shù)的使用方式

    文章介紹了Docker中的數(shù)據(jù)卷Volume的概念及其在宿主機和容器之間的數(shù)據(jù)共享和持久化,它詳細說明了兩種數(shù)據(jù)掛載方式:通過宿主機絕對路徑掛載和通過卷標(biāo)映射掛載,包括匿名掛載和具名掛載,同時,文章還展示了如何通過docker命令查看數(shù)據(jù)卷的宿主機目錄
    2024-11-11
  • n8n搭建docker部署教程

    n8n搭建docker部署教程

    文章指導(dǎo)如何通過Docker搭建n8n,包含更換鏡像源、修改daemon.json配置、下載1.8.2版本及使用docker-compose.yml和.env文件部署的步驟,旨在提升部署效率與便捷性
    2025-07-07
  • Ubuntu16.04Docker的CS模式詳細介紹

    Ubuntu16.04Docker的CS模式詳細介紹

    這篇文章主要介紹了Ubuntu16.04Docker的CS模式詳細介紹的相關(guān)資料,這里對Docker CS模式圖文詳細介紹,需要的朋友可以參考下
    2016-12-12
  • Docker images導(dǎo)出和導(dǎo)入操作

    Docker images導(dǎo)出和導(dǎo)入操作

    這篇文章主要介紹了Docker images導(dǎo)出和導(dǎo)入操作,具有很好的參考價值,希望對大家有所幫助。一起跟隨小編過來看看吧
    2021-03-03
  • Docker安裝Nginx教程實現(xiàn)圖例講解

    Docker安裝Nginx教程實現(xiàn)圖例講解

    這篇文章主要介紹了Docker安裝Nginx教程圖例講解,文中通過示例代碼介紹的非常詳細,對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友可以參考下
    2020-09-09
  • 詳解如何將docker快速升級到最新版本

    詳解如何將docker快速升級到最新版本

    最近在對區(qū)塊鏈瀏覽器調(diào)優(yōu),該區(qū)塊鏈瀏覽器就是使用docker部署的微服務(wù),在一臺新的服務(wù)器上啟動時報錯,發(fā)現(xiàn)是docker版本過低,所以本文給大家介紹了將docker快速升級到最新版本的方法,需要的朋友可以參考下
    2024-02-02
  • Docker部署Memos服務(wù)的實現(xiàn)

    Docker部署Memos服務(wù)的實現(xiàn)

    本文將介紹如何使用Docker部署Memos服務(wù),首先,我們將構(gòu)建Memos服務(wù)的Docker鏡像,然后將在Docker容器中運行Memos服務(wù),感興趣的可以了解一下
    2023-12-12
  • Docker從json-file到syslog的集中化管理實戰(zhàn)指南

    Docker從json-file到syslog的集中化管理實戰(zhàn)指南

    本次實戰(zhàn)通過對比 json-file 與 syslog 兩種日志驅(qū)動,演示了 Docker 容器日志的本地存儲與系統(tǒng)日志集成方式,并成功將默認日志驅(qū)動全局配置為 syslog,實現(xiàn)日志集中化管理,感興趣的朋友跟隨小編一起看看吧
    2025-12-12
  • 詳解如何將java項目打包成docker鏡像并且可運行

    詳解如何將java項目打包成docker鏡像并且可運行

    java?項目打包成?Docker?可運行的鏡像,其目的是便于運用docker容器來管理項目,文中的示例代碼講解詳細,感興趣的小伙伴可以了解一下
    2024-11-11

最新評論

达尔| 松潘县| 衡阳县| 中宁县| 保定市| 香港| 泰和县| 新河县| 墨竹工卡县| 宣威市| 文山县| 嘉鱼县| 长丰县| 华安县| 望谟县| 微山县| 沁水县| 文山县| 恭城| 安仁县| 沁源县| 万年县| 永德县| 韩城市| 南宫市| 漳州市| 江阴市| 老河口市| 东乌| 西藏| 孝义市| 景泰县| 乌鲁木齐县| 宁安市| 南陵县| 宝坻区| 克拉玛依市| 夏河县| 西林县| 广昌县| 沛县|