harbor

goharborApache-2.0活跃维护

开源的可信云原生镜像仓库,用来存储、签名和扫描容器镜像,帮团队在 Kubernetes 环境里安全地管理和分发制品。

An open source trusted cloud native registry project that stores, signs, and scans content.

v2.16.0发布于 2026-11-09 07:47 UTC29,712star +20 / 7 天5,414fork同步于 2026-11-10 17:21 UTC

怎么上手

由 README 提炼,执行前请确认
下载 Harbor release 二进制包后按官方 Installation & Configuration Guide 安装;Kubernetes 场景使用 https://github.com/goharbor/harbor-helm
硬件要求按 README 说明

README 未说明具体硬件配置;仅要求 Linux 主机上 Docker 20.10.10-ce+ 与 docker-compose 1.18.0+,Kubernetes 部署请使用 Harbor Helm Chart。

有 Docker 镜像
下载:源码 zip·GitHub Releases(安装包)本站不镜像安装包

项目说明

由 README 自动翻译提炼

CNCF 托管的开源可信云原生镜像仓库,在 Docker Distribution 基础上补齐安全、身份与管理能力

开源的可信云原生镜像仓库,用来存储、签名和扫描容器镜像,帮团队在 Kubernetes 环境里安全地管理和分发制品。

核心能力

  • 同时托管容器镜像与 Helm Chart
  • 按项目做基于角色的访问控制(RBAC)
  • 基于策略在多个仓库实例间复制镜像并自动重试
  • 定期扫描镜像漏洞并按策略阻止有风险镜像部署
  • 集成 LDAP/AD 与 OIDC 实现企业认证和单点登录

容易踩的坑

main 分支可能不稳定甚至不可用,应使用 releases 中的稳定版本;需按官方安装配置指南完成部署,不能仅靠 docker-compose 直接起;v2.15.0 起发布包用 Cosign 签名,校验需 Cosign v2.0+。

内容由模型根据 README 生成,可能不完整或不准确,以官方文档为准。看原文 README

最近发版

5 个版本v2.16.0
  1. v2.16.0最新正式版2026-11-09 · 2026-11-09 07:47 UTC

    What's Changed

    Exciting New Features 🎉

    Enhancement 🚀

    Component updates ⬆️

  2. v2.16.0-rc2pre-release2026-11-06 · 2026-11-06 12:30 UTC
    查看更新说明

    What's Changed

    Exciting New Features 🎉

    Enhancement 🚀

    Component updates ⬆️

  3. v2.16.0-rc1pre-release2026-10-27 · 2026-10-27 07:25 UTC
    查看更新说明

    What's Changed

    Exciting New Features 🎉

    Enhancement 🚀

    Component updates ⬆️

  4. v2.14.62026-10-23 · 2026-10-23 07:04 UTC
    查看更新说明

    What's Changed

    Component updates ⬆️

    Full Changelog: https://github.com/goharbor/harbor/compare/v2.14.5...v2.14.6

  5. v2.14.6-rc2pre-release2026-10-22 · 2026-10-22 09:28 UTC
    查看更新说明

    What's Changed

    Component updates ⬆️

    Full Changelog: https://github.com/goharbor/harbor/compare/v2.14.5...v2.14.6-rc2

用户点评

登录用户的真实使用记录,可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译

    Harbor

    CI Go Report Card Coverage Status CII Best Practices Codacy Badge Code scanning - action OCI Distribution Conformance Tests FOSSA Status Helm Chart on Artifact Hub OpenSSF Scorecard

    notificationCommunity Meeting
    The Harbor Project holds bi-weekly community calls in two different timezones. To join the community calls or to watch previous meeting notes and recordings, please visit the meeting schedule.

    Note: The main branch may be in an unstable or even broken state during development. Please use releases instead of the main branch in order to get a stable set of binaries.

    Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Harbor extends the open source Docker Distribution by adding the functionalities usually required by users such as security, identity and management. Having a registry closer to the build and run environment can improve the image transfer efficiency. Harbor supports replication of images between registries, and also offers advanced security features such as user management, access control and activity auditing.

    Harbor is hosted by the Cloud Native Computing Foundation (CNCF). If you are an organization that wants to help shape the evolution of cloud native technologies, consider joining the CNCF. For details about who is involved and how Harbor plays a role, read the CNCF announcement.

    Features

    • Cloud native registry: With support for both container images and Helm charts, Harbor serves as registry for cloud native environments like container runtimes and orchestration platforms.
    • Role based access control: Users access different repositories through 'projects' and a user can have different permission for images or Helm charts under a project.
    • Policy based replication: Images and charts can be replicated (synchronized) between multiple registry instances based on policies with using filters (repository, tag and label). Harbor automatically retries a replication if it encounters any errors. This can be used to assist loadbalancing, achieve high availability, and facilitate multi-datacenter deployments in hybrid and multi-cloud scenarios.
    • Vulnerability Scanning: Harbor scans images regularly for vulnerabilities and has policy checks to prevent vulnerable images from being deployed.
    • LDAP/AD support: Harbor integrates with existing enterprise LDAP/AD for user authentication and management, and supports importing LDAP groups into Harbor that can then be given permissions to specific projects.
    • OIDC support: Harbor leverages OpenID Connect (OIDC) to verify the identity of users authenticated by an external authorization server or identity provider. Single sign-on can be enabled to log into the Harbor portal.
    • Image deletion & garbage collection: System administrators can run garbage collection jobs so that images (dangling manifests and unreferenced blobs) can be deleted and their space can be freed up periodically.
    • Graphical user portal: User can easily browse, search repositories and manage projects.
    • Auditing: All the operations to the repositories are tracked through logs.
    • RESTful API: RESTful APIs are provided to facilitate administrative operations, and are easy to use for integration with external systems. An embedded Swagger UI is available for exploring and testing the API.
    • Easy deployment: Harbor can be deployed via Docker compose as well Helm Chart, and a Harbor Operator was added recently as well.

    Architecture

    For learning the architecture design of Harbor, check the document Architecture Overview of Harbor.

    API

    • Harbor RESTful API: The APIs for most administrative operations of Harbor and can be used to perform integrations with Harbor programmatically.

    Install & Run

    System requirements:

    On a Linux host: docker 20.10.10-ce+ and docker-compose 1.18.0+.

    Download binaries of Harbor release and follow Installation & Configuration Guide to install Harbor.

    If you want to deploy Harbor on Kubernetes, please use the Harbor chart.

    Refer to the documentation for more details on how to use Harbor.

    Verifying Release Signatures

    Starting with v2.15.0, Harbor release artifacts are cryptographically signed using Cosign to ensure authenticity and integrity.

    Download the installers and signature bundles from the Harbor releases page.

    Quick Verification
    # Install Cosign (v2.0+)
    brew install sigstore/tap/cosign
    
    # Verify signature
    cosign verify-blob \
      --bundle harbor-offline-installer-v2.15.0.tgz.sigstore.json \
      --certificate-oidc-issuer https://token.actions.githubusercontent.com \
      --certificate-identity-regexp '^https://github.com/goharbor/harbor/.github/workflows/publish_release.yml@refs/tags/v.*$' \
      harbor-offline-installer-v2.15.0.tgz
    

    OCI Distribution Conformance Tests

    Check the OCI distribution conformance tests report of Harbor.

    Compatibility

    The compatibility list document provides compatibility information for the Harbor components.

    Community

    Demos

    • Live Demo - A demo environment with the latest Harbor stable build installed. For additional information please refer to this page.
    • Video Demos - Demos for Harbor features and continuously updated.

    Partners and Users

    For a list of users, please refer to ADOPTERS.md.

    Security

    Security Audit

    A third party security audit was performed by Cure53 in October 2019. You can see the full report here.

    Reporting security vulnerabilities

    If you've found a security related issue, a vulnerability, or a potential vulnerability in Harbor, do not file a public issue. Report it privately via GitHub private vulnerability reporting: open the Security tab and click Report a vulnerability. The Harbor Security Team will acknowledge your report, and will follow up in the advisory thread once we've identified the issue positively or negatively.

    For further details please see our complete security release process.

    License

    Harbor is available under the Apache 2 license.

    This project uses open source components which have additional licensing terms. The official docker images and licensing terms for these open source components can be found at the following locations:

    Fossa Status

    FOSSA Status