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. With Harbor, the images are stored within the private registry, keeping the bits and intellectual properties behind the company firewall. 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.
Image replication: Images can be replicated (synchronized) between multiple registry instances. Great for load balancing, high availability, hybrid and multi-cloud scenarios.
Graphical user portal: User can easily browse, search repositories and manage projects.
AD/LDAP support: Harbor integrates with existing enterprise AD/LDAP for user authentication and management.
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: docker compose and offline installer.

Install

System requirements: Harbor only works with docker 1.10.0+ and docker-compose 1.6.0+.

Install via docker compose

On an Internet connected host, Harbor can be easily installed via docker-compose:

Get the source code:

$ git clone https://github.com/vmware/harbor

Edit the file make/harbor.cfg, make necessary configuration changes such as hostname, admin password and mail server. Refer to Installation and Configuration Guide for more info.

Install Harbor with the following methods. Note that the build container images process can take a while.

I: Automation Install

$ make install

II: Manual Install

$ cd make

$ ./prepare
Generated configuration file: ./config/ui/env
Generated configuration file: ./config/ui/app.conf
Generated configuration file: ./config/registry/config.yml
Generated configuration file: ./config/db/env

$ cd dev

$ docker-compose up -d

Install via offline installer

For those who do not want to clone the source, or need to install Harbor on a server not connected to the Internet, there is a pre-built installation package available. For details on how to download and use the installation package, please refer to Installation and Configuration Guide.

After installation

If everything worked properly, you should be able to open a browser to visit the admin portal at http://reg.yourdomain.com. Note that the default administrator username/password are admin/Harbor12345.

Log in to the admin portal and create a new project, e.g. myproject. You can then use docker commands to login and push images (by default, the registry server listens on port 80):

$ docker login reg.yourdomain.com
$ docker push reg.yourdomain.com/myproject/myrepo:mytag

Upgrade

If you are upgrading Harbor from an older version with existing data, you need to migrate the data to fit the new database schema. For more details, please refer to Data Migration Guide.

Run

For information on how to use Harbor, please take a look at User Guide.

Community

Get connected with Project Harbor's community and sign up with VMware {code} https://code.vmware.com/join/ to get invited to VMware {code} Slack group, Channel: #harbor. Email: harbor @ vmware.com .

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.

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: