-
Notifications
You must be signed in to change notification settings - Fork 7.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
trusted-content: restructure doi section
Signed-off-by: David Karlsson <[email protected]>
- Loading branch information
Showing
12 changed files
with
219 additions
and
105 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
description: Guidelines for Official Images on Docker Hub | ||
keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, | ||
official,image, documentation | ||
title: Docker Official Images | ||
aliases: | ||
- /docker-hub/official_repos/ | ||
- /docker-hub/official_images/ | ||
--- | ||
|
||
The [Docker Official Images](https://hub.docker.com/search?q=&type=image&image_filter=official) | ||
are a curated set of Docker repositories hosted on Docker Hub. | ||
|
||
These images provide essential base repositories that serve as the starting | ||
point for the majority of users. | ||
|
||
These include operating systems such as | ||
[Ubuntu](https://hub.docker.com/_/ubuntu/) and | ||
[Alpine](https://hub.docker.com/_/alpine/), programming languages such as | ||
[Python](https://hub.docker.com/_/python) and | ||
[Node](https://hub.docker.com/_/node), and other essential tools such as | ||
[memcached](https://hub.docker.com/_/memcached) and | ||
[MySQL](https://hub.docker.com/_/mysql). | ||
|
||
The images are some of the [most secure images](https://www.docker.com/blog/enhancing-security-and-transparency-with-docker-official-images/) | ||
on Docker Hub. This is particularly important as Docker Official Images are | ||
some of the most popular on Docker Hub. Typically, Docker Official images have | ||
few or no vulnerabilities. | ||
|
||
The images exemplify [`Dockerfile` best practices](../../develop/develop-images/dockerfile_best-practices.md) | ||
and provide clear documentation to serve as a reference for other `Dockerfile` authors. | ||
|
||
Images that are part of this program have a special badge on Docker Hub making | ||
it easier for you to identify projects that are official Docker images. | ||
|
||
![Docker official image badge](../images/official-image-badge-iso.png) | ||
|
||
## In this section | ||
|
||
{{% sectionlinks %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
--- | ||
title: Contributing to Docker Official Images | ||
description: | | ||
This article describes how Docker Official Images are created, | ||
and how you can contribute or leave feedback. | ||
keywords: docker official images, doi, contributing, upstream, open source | ||
--- | ||
|
||
Docker, Inc. sponsors a dedicated team that's responsible for reviewing and | ||
publishing all content in Docker Official Images. This team works in | ||
collaboration with upstream software maintainers, security experts, and the | ||
broader Docker community. | ||
|
||
While it's preferable to have upstream software authors maintaining their | ||
Docker Official Images, this isn't a strict requirement. Creating | ||
and maintaining images for Docker Official Images is a collaborative process. | ||
It takes place [openly on GitHub](https://github.com/docker-library/official-images) | ||
where participation is encouraged. Anyone can provide feedback, contribute | ||
code, suggest process changes, or even propose a new Official Image. | ||
|
||
> **Note** | ||
> | ||
> Docker Official Images are the intellectual property of Docker. | ||
## Creating a Docker Official Image | ||
|
||
From a high level, an Official Image starts out as a proposal in the form | ||
of a set of GitHub pull requests. The following GitHub repositories detail the proposal requirements: | ||
|
||
- [Docker Official Images repository on GitHub](https://github.com/docker-library/official-images#readme) | ||
- [Documentation for Docker Official Images](https://github.com/docker-library/docs#readme) | ||
|
||
The Docker Official Images team, with help from community contributors, formally | ||
review each proposal and provide feedback to the author. This initial review | ||
process may require a bit of back-and-forth before the proposal is accepted. | ||
|
||
There are subjective considerations during the review process. These | ||
subjective concerns boil down to the basic question: "is this image generally | ||
useful?" For example, the [Python](https://hub.docker.com/_/python/) | ||
Docker Official Image is "generally useful" to the larger Python developer | ||
community, whereas an obscure text adventure game written in Python last week is | ||
not. | ||
|
||
Once a new proposal is accepted, the author is responsible for keeping their | ||
images and documentation up-to-date and responding to user feedback. Docker is | ||
responsible for building and publishing the images on Docker Hub. Updates to | ||
Docker Official Images follow the same pull request process as for new images, | ||
although review process for updates is more streamlined. The Docker Official | ||
Images team ultimately acts as a gatekeeper for all changes, which helps | ||
ensures consistency, quality, and security. | ||
|
||
## Submitting feedback for Docker Official Images | ||
|
||
All Docker Official Images contain a **User Feedback** section in their | ||
documentation which covers the details for that specific repository. In most | ||
cases, the GitHub repository which contains the Dockerfiles for an Official | ||
Repository also has an active issue tracker. General feedback and support | ||
questions should be directed to `#docker-library` on [Libera.Chat IRC](https://libera.chat). |
Oops, something went wrong.