![]() ![]() ![]() If you do not represent upstream and upstream becomes interested in maintaining the image, steps should be taken to ensure a smooth transition of image maintainership over to upstream.įor upstreams interested in taking over maintainership of an existing repository, the first step is to get involved in the existing repository. Version bumps and security fixes should be attended to in a timely manner. While some of that standard is hard to define (due to subjectivity), as much as possible is defined here, while also adhering to the "Best Practices" where appropriate.Ī checklist which may be used by the maintainers during review can be found in NEW-IMAGE-CHECKLIST.md. Review Guidelinesīecause the official images are intended to be learning tools for those new to Docker as well as the base images for advanced users to build their production releases, we review each proposed Dockerfile to ensure that it meets a minimum standard for quality and maintainability. Please be prepared to submit a PR there as well, pending acceptance of your image here. If you'd like the review process to go more smoothly, please ensure that your Dockerfiles adhere to all the points mentioned there, as well as below, before submitting a pull request.Īlso, the Hub descriptions for these images are currently stored separately in the docker-library/docs repository, whose README.md file explains more about how it's structured and how to contribute to it. These will be the foundation of the review process performed by the official images maintainers. Thank you for your interest in the Docker official images project! We strive to make these instructions as simple and straightforward as possible, but if you find yourself lost, don't hesitate to seek us out on Libera.Chat IRC in channel #docker-library or by creating a GitHub issue here.īe sure to familiarize yourself with Official Repositories on Docker Hub and the Best practices for writing Dockerfiles in the Docker documentation. Yes! We have a dedicated FAQ repository where we try to collect other common questions (both about the program and about our practices). See the multi-arch section below for recommendations in adding more architectures to an official image. If you're curious about how these are built, head over to to see the build scaffolding. Other architectures built by official images: (but not officially supported by Docker, Inc.)Īs of, these other architectures are included under the non-prefixed images via "manifest lists" (also known as "indexes" in the OCI image specification), such that, for example, docker run hello-world should run as-is on all supported platforms.Architectures officially supported by Docker, Inc.Some images have been ported for other architectures, and many of these are officially supported (to various degrees). (If you are a representative of an upstream for which there exists an image and you would like to get involved, please see the Maintainership section below!) Architectures other than amd64? Additionally we aim to exemplify the best practices for Dockerfiles to serve as a reference when making or deriving your own images from them. Many images are maintained in collaboration with the relevant upstream project if not maintained directly by them. In essence we strive to heed upstream's recommendations on how they intend for their software to be consumed. See Docker's documentation for a good high-level overview of the program. The main tenets are:Īctively rebuild for updates and security fixesĪdd minimal quality-of-life behavior for the container environment where fit The Docker Official Images are curated images hosted on Docker Hub. ![]() Change to a tag in an existing repository (that you're the maintainer of).Adding a new tag in an existing repository (that you're the maintainer of). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |