An open source trusted cloud native registry project that stores, signs, and scans content.
Go to file
Daniel Jiang 0da29e5305 Merge pull request #688 from reasonerjt/dev
jsminify's basedir should be configurable
2016-08-17 16:54:32 +08:00
.github provide issue template 2016-04-22 15:04:29 +08:00
api Merge pull request #682 from ywk253100/policy_deletion 2016-08-17 16:54:15 +08:00
auth add *_empty_test.go for actual go test coverage 2016-07-29 18:39:29 +08:00
contrib update prebuilt 2016-08-03 15:48:20 +08:00
controllers merge with master 2016-08-03 17:15:00 +08:00
dao 1. support policy deletion 2. bug fix: missing semicolon in js 2016-08-12 17:59:25 +08:00
Deploy Merge pull request #688 from reasonerjt/dev 2016-08-17 16:54:32 +08:00
docs Update swagger.yaml 2016-08-12 15:12:35 +08:00
job Use AES to encrypt password for target 2016-08-04 11:35:52 +08:00
jobservice add *_empty_test.go for actual go test coverage 2016-07-29 18:39:29 +08:00
migration 1. support policy deletion 2. bug fix: missing semicolon in js 2016-08-12 17:59:25 +08:00
models 1. support policy deletion 2. bug fix: missing semicolon in js 2016-08-12 17:59:25 +08:00
service merge with master 2016-08-10 15:34:23 +08:00
static 1. support policy deletion 2. bug fix: missing semicolon in js 2016-08-12 17:59:25 +08:00
tests add new structs from swagger auto gen code 2016-08-15 14:36:42 +08:00
ui add *_empty_test.go for actual go test coverage 2016-07-29 18:39:29 +08:00
utils add UT for package utils 2016-08-11 17:58:17 +08:00
vendor Merge master into dev 2016-08-15 11:30:06 +08:00
views add paginator, add pagination to the logs. 2016-08-05 20:37:58 +08:00
.gitignore statemachine and schduler to support retry 2016-07-05 11:42:30 +08:00
.travis.yml Merge master into dev 2016-08-15 11:30:06 +08:00
AUTHORS update roadmap 2016-06-03 16:57:38 +08:00
Dockerfile.job Merge master into dev 2016-08-15 11:30:06 +08:00
Dockerfile.ui rebuild vendor directory 2016-08-12 14:50:00 +08:00
favicon.ico added favicon.ico for Harbor 2016-03-11 14:34:56 +08:00
LICENSE update README, LICENSE, and bump to registry/2.3.0 2016-03-01 18:21:56 +08:00
NOTICE add NOTICE, update README.md 2016-03-03 10:15:12 +08:00
README.md merge with master 2016-08-10 15:34:23 +08:00
ROADMAP.md update roadmap 2016-06-03 17:03:58 +08:00

Harbor

Build Status Coverage Status

alg tag

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.
  • Internationalization: Already localized for English, Chinese, German, Japanese and Russian. More languages can be added.
  • 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:

  1. Get the source code:

    $ git clone https://github.com/vmware/harbor
    
  2. Edit the file Deploy/harbor.cfg, make necessary configuration changes such as hostname, admin password and mail server. Refer to Installation and Configuration Guide for more info.

  3. Install Harbor with the following commands. Note that the docker-compose process can take a while.

    $ cd Deploy
    
    $ ./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
    
    $ 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

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.

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.

Partners

DataMan     SlamTec     CaiCloud

Users

MaDaiLiCai Dianrong

Supporting Technologies

beego Harbor is powered by Beego.

About

Project Harbor is initiated by the Advanced Technology Center (ATC), VMware China R&D as a Cloud Application Accelerator (CAA) project.