An open source trusted cloud native registry project that stores, signs, and scans content.
Go to file
2017-07-14 14:53:12 +08:00
.github update README 2016-12-29 15:02:44 +08:00
contrib Upgrade python SDK to v1.1.1 2017-05-04 04:10:13 -07:00
docs Update swagger.yaml 2017-06-30 15:27:32 +08:00
make Clair photon (#2721) 2017-07-10 21:00:44 -07:00
src fix bug 2017-07-14 14:53:12 +08:00
tests Merge pull request #2631 from ywk253100/170626_statistic 2017-06-30 14:26:15 +08:00
tools update user realname 2017-07-05 03:43:21 -07:00
.gitignore Improve components and change package.json 2017-06-21 09:53:59 +08:00
.travis.yml Upgrade UI builder to 1.2.7 2017-06-27 18:33:53 +08:00
AUTHORS update documents (#2020) 2017-04-17 13:46:39 +08:00
CHANGELOG.md update documents (#2020) 2017-04-17 13:46:39 +08:00
CONTRIBUTING.md update README 2016-11-08 22:37:18 +08:00
LICENSE update license and notice 2017-05-05 18:54:35 +08:00
Makefile Clair photon (#2721) 2017-07-10 21:00:44 -07:00
NOTICE update license and notice 2017-05-05 18:54:35 +08:00
partners.md update README 2016-12-29 15:05:55 +08:00
README.md update badge on README 2017-05-09 17:08:13 +08:00
ROADMAP.md update documents (#2020) 2017-04-17 13:46:39 +08:00
VERSION add version file 2017-03-21 18:39:09 -07:00

Harbor

Build Status Coverage Status

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

Harbor

Project Harbor is an enterprise-class registry server that stores and distributes Docker images. Harbor extends the open source Docker Distribution by adding the functionalities usually required by an enterprise, such as security, identity and management. As an enterprise private registry, Harbor offers better performance and security. Having a registry closer to the build and run environment improves the image transfer efficiency. Harbor supports the setup of multiple registries and has images replicated between them. In addition, Harbor offers advanced security features, such as user management, access control and activity auditing.

Features

  • Role based access control: Users and repositories are organized via 'projects' and a user can have different permission for images under a project.
  • Policy based image replication: Images can be replicated (synchronized) between multiple registry instances. Great for load balancing, high availability, multi-datacenter, hybrid and multi-cloud scenarios.
  • LDAP/AD support: Harbor integrates with existing enterprise LDAP/AD for user authentication and management.
  • Image deletion & garbage collection: Images can be deleted and their space can be recycled.
  • Notary: Image authenticity can be ensured.
  • Graphical user portal: User can easily browse, search repositories and manage projects.
  • Auditing: All the operations to the repositories are tracked.
  • RESTful API: RESTful APIs for most administrative operations, easy to integrate with external systems.
  • Easy deployment: Provide both an online and offline installer.

Install & Run

System requirements:

On a Linux host: docker 1.10.0+ and docker-compose 1.6.0+ .

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

Refer to User Guide for more details on how to use Harbor.

Community

Slack: Join Harbor's community here: VMware {code}, Channel: #harbor.
Email: harbor@ vmware.com .
WeChat Group: Add WeChat id connect1688 to join WeChat discussion group.
More info on partners and users.

Contribution

We welcome contributions from the community. If you wish to contribute code and you have not signed our contributor license agreement (CLA), our bot will update the issue when you open a pull request. For any questions about the CLA process, please refer to our FAQ. Contact us for any questions: harbor @vmware.com .

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: