An open source trusted cloud native registry project that stores, signs, and scans content.
Go to file
Daniel Jiang a05f1e3507 Merge pull request #1700 from ywk253100/170321_mount_data
Read capacity from adminserver
2017-03-21 16:42:32 +08:00
.github update README 2016-12-29 15:02:44 +08:00
contrib remove v1 flag in getManifestWithConf 2017-01-04 15:11:16 +08:00
docs Merge latest updates. 2017-03-21 11:51:12 +08:00
make read capacity from adminserver 2017-03-21 16:28:24 +08:00
src fix merge issue 2017-03-21 16:29:51 +08:00
tests read capacity from adminserver 2017-03-21 16:28:24 +08:00
tools remove openldap lib from Dockerfile and support build with offcial golang image(1.7.3) 2017-01-04 17:48:20 +08:00
.gitignore Updates for new UI latest changes. 2017-03-21 14:20:32 +08:00
.travis.yml Merge latest updates. 2017-03-21 11:51:12 +08:00
AUTHORS update authors 2016-11-22 22:13:49 +08:00
CHANGELOG.md update change log 2016-11-02 21:27:04 +08:00
CONTRIBUTING.md update README 2016-11-08 22:37:18 +08:00
LICENSE update license for 0.5.0 2016-11-28 13:02:16 +08:00
Makefile Merge latest updates. 2017-03-21 11:51:12 +08:00
NOTICE update license for 0.5.0 2016-11-28 13:02:16 +08:00
partners.md update README 2016-12-29 15:05:55 +08:00
README.md update README 2016-12-29 15:05:55 +08:00
ROADMAP.md ROADMAP 2016-11-02 21:48:47 +08:00

Harbor

Build Status Coverage Status

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.
  • 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. Besides, a virtual appliance for vSphere platform (OVA) is available.

Install & Run

System requirements:

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

On vSphere: vCenter 5.5+ for deployment of Harbor's virtual appliance.

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: