An open source trusted cloud native registry project that stores, signs, and scans content.
Go to file
Daniel Jiang 2eb1845ae4 Merge pull request #556 from ywk253100/bug_fixes
bug fix: job enters an endless loop when user has no role to project on destination
2016-07-15 17:29:20 +08:00
.github provide issue template 2016-04-22 15:04:29 +08:00
Deploy fix spell error 2016-07-15 17:22:56 +08:00
api close connection immediately when it is not used anymore 2016-07-14 18:15:24 +08:00
auth change code as the review reqired 2016-06-02 17:33:10 +08:00
contrib update docs 2016-05-17 22:04:16 +08:00
controllers rename key about JS compression. 2016-07-14 14:55:36 +08:00
dao order jobs by update time 2016-07-14 17:54:25 +08:00
docs Merge pull request #545 from yhua123/patch-1 2016-07-15 15:00:35 +08:00
job Merge pull request #556 from ywk253100/bug_fixes 2016-07-15 17:29:20 +08:00
jobservice statemachine and schduler to support retry 2016-07-05 11:42:30 +08:00
migration update readme, migration guide 2016-07-13 15:42:47 +08:00
models return count of jobs which are failed when listing policies 2016-07-05 18:57:04 +08:00
service Merge pull request #443 from ywk253100/dev 2016-06-29 18:46:42 +08:00
static add resizable height in replication page. 2016-07-14 20:43:58 +08:00
tests fix build issue 2016-07-14 21:22:39 +08:00
ui add new page for change password 2016-07-06 13:09:32 +08:00
utils close connection immediately when it is not used anymore 2016-07-14 18:15:24 +08:00
vendor upgrade beego to 1.6.1 2016-06-27 17:38:50 +08:00
views add JS minification when building UI image. 2016-07-13 17:23:43 +08:00
.gitignore statemachine and schduler to support retry 2016-07-05 11:42:30 +08:00
.travis.yml Update .travis.yml 2016-06-15 12:14:45 +08:00
AUTHORS update roadmap 2016-06-03 16:57:38 +08:00
Dockerfile.job move app.conf to Deploy folder 2016-06-30 18:42:35 +08:00
Dockerfile.ui add JS minification when building UI image. 2016-07-13 17:23:43 +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 update readme, migration guide 2016-07-13 15:42:47 +08:00
ROADMAP.md update roadmap 2016-06-03 17:03:58 +08:00
favicon.ico added favicon.ico for Harbor 2016-03-11 14:34:56 +08:00

README.md

Harbor

Build Status

alg tag

Project Harbor is initiated by VMware China R&D as a Cloud Application Accelerator (CAA) project. CAA provides a set of tools to improve the productivity of cloud developers in China and other countries. CAA includes tools like registry server, mirror server, decentralized image distributor, etc.

Project Harbor is an enterprise-class registry server, which extends the open source Docker Registry server by adding the functionality usually required by an enterprise, such as security, control, and management. Harbor is primarily designed to be a private registry - providing the needed security and control that enterprises require. It also helps minimize bandwidth usage, which is helpful to both improve productivity (local network access) as well as performance (for those with poor internet connectivity).

Features

  • Role based access control: Users and Docker repositories are organized via "projects", 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 and distributed data centers.
  • Graphical user portal: User can easily browse, search Docker repositories, manage projects/namespaces.
  • 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, easing intergration with external management platforms.

Getting Started

Harbor is self-contained and can be easily deployed via docker-compose (Quick-Start steps below). Refer to the Installation and Configuration Guide for detailed information.

System requirements:
Harbor only works with docker 1.10+ and docker-compose 1.6.0+, and an internet-connected host.

  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
    

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

Data migration:

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

NOTE:
For those who don't 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 this installation package, please refer to Installation and Configuration Guide .

For information on how to use Harbor, please see User Guide .

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, an open source framework to build and develop applications in the Go way.