github.com/iamlotus/docker@v1.8.1/docs/docker-hub/official_repos.md (about)

     1  <!--[metadata]>
     2  +++
     3  title = "Official Repositories on Docker Hub"
     4  description = "Guidelines for Official Repositories on Docker Hub"
     5  keywords = ["Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, official, image,  documentation"]
     6  [menu.main]
     7  parent = "smn_pubhub"
     8  weight = 4
     9  +++
    10  <![end-metadata]-->
    11  
    12  # Official Repositories on Docker Hub
    13  
    14  The Docker [Official Repositories](http://registry.hub.docker.com/official) are
    15  a curated set of Docker repositories that are promoted on Docker Hub. They are
    16  designed to:
    17  
    18  * Provide essential base OS repositories (for example,
    19    [`ubuntu`](https://registry.hub.docker.com/_/ubuntu/),
    20    [`centos`](https://registry.hub.docker.com/_/centos/)) that serve as the
    21    starting point for the majority of users.
    22  
    23  * Provide drop-in solutions for popular programming language runtimes, data
    24    stores, and other services, similar to what a Platform-as-a-Service (PAAS)
    25    would offer.
    26  
    27  * Exemplify [`Dockerfile` best practices](/articles/dockerfile_best-practices)
    28    and provide clear documentation to serve as a reference for other `Dockerfile`
    29    authors.
    30  
    31  * Ensure that security updates are applied in a timely manner. This is
    32    particularly important as many Official Repositories are some of the most
    33    popular on Docker Hub.
    34  
    35  * Provide a channel for software vendors to redistribute up-to-date and
    36    supported versions of their products. Organization accounts on Docker Hub can
    37    also serve this purpose, without the careful review or restrictions on what
    38    can be published.
    39  
    40  Docker, Inc. sponsors a dedicated team that is responsible for reviewing and
    41  publishing all Official Repositories content. This team works in collaboration
    42  with upstream software maintainers, security experts, and the broader Docker
    43  community.
    44  
    45  While it is preferable to have upstream software authors maintaining their
    46  corresponding Official Repositories, this is not a strict requirement. Creating
    47  and maintaining images for Official Repositories is a public process. It takes
    48  place openly on GitHub where participation is encouraged. Anyone can provide
    49  feedback, contribute code, suggest process changes, or even propose a new
    50  Official Repository.
    51  
    52  ## Should I use Official Repositories?
    53  
    54  New Docker users are encouraged to use the Official Repositories in their
    55  projects. These repositories have clear documentation, promote best practices,
    56  and are designed for the most common use cases. Advanced users are encouraged to
    57  review the Official Repositories as part of their `Dockerfile` learning process.
    58  
    59  A common rationale for diverging from Official Repositories is to optimize for
    60  image size. For instance, many of the programming language stack images contain
    61  a complete build toolchain to support installation of modules that depend on
    62  optimized code. An advanced user could build a custom image with just the
    63  necessary pre-compiled libraries to save space.
    64  
    65  A number of language stacks such as
    66  [`python`](https://registry.hub.docker.com/_/python/) and
    67  [`ruby`](https://registry.hub.docker.com/_/ruby/) have `-slim` tag variants
    68  designed to fill the need for optimization.  Even when these "slim" variants are
    69  insufficient, it is still recommended to inherit from an Official Repository
    70  base OS image to leverage the ongoing maintenance work, rather than duplicating
    71  these efforts.
    72  
    73  ## How can I get involved?
    74  
    75  All Official Repositories contain a **User Feedback** section in their
    76  documentation which covers the details for that specific repository. In most
    77  cases, the GitHub repository which contains the Dockerfiles for an Official
    78  Repository also has an active issue tracker. General feedback and support
    79  questions should be directed to `#docker-library` on Freenode IRC.
    80  
    81  ## How do I create a new Official Repository?
    82  
    83  From a high level, an Official Repository starts out as a proposal in the form
    84  of a set of GitHub pull requests.  You'll find detailed and objective proposal
    85  requirements in the following GitHub repositories:
    86  
    87  * [docker-library/official-images](https://github.com/docker-library/official-images)
    88  
    89  * [docker-library/docs](https://github.com/docker-library/docs)
    90  
    91  The Official Repositories team, with help from community contributors, formally
    92  review each proposal and provide feedback to the author. This initial review
    93  process may require a bit of back and forth before the proposal is accepted.
    94  
    95  There are also subjective considerations during the review process. These
    96  subjective concerns boil down to the basic question: "is this image generally
    97  useful?"  For example, the [`python`](https://registry.hub.docker.com/_/python/)
    98  Official Repository is "generally useful" to the large Python developer
    99  community, whereas an obscure text adventure game written in Python last week is
   100  not.
   101  
   102  When a new proposal is accepted, the author becomes responsible for keeping
   103  their images up-to-date and responding to user feedback.  The Official
   104  Repositories team becomes responsible for publishing the images and
   105  documentation on Docker Hub.  Updates to the Official Repository follow the same
   106  pull request process, though with less review. The Official Repositories team
   107  ultimately acts as a gatekeeper for all changes, which helps mitigate the risk
   108  of quality and security issues from being introduced.
   109  
   110  > **Note**: If you are interested in proposing an Official Repository, but would
   111  > like to discuss it with Docker, Inc. privately first, please send your
   112  > inquiries to partners@docker.com.  There is no fast-track or pay-for-status
   113  > option.