What is this?
This repository contains the image documentation for each of the Docker Official Images. See docker-library/official-images for more information about the program in general.
All Markdown files here are run through tianon's fork of
markdownfmt, and verified as formatted correctly via GitHub Actions.
Table of Contents
- What is this?
- How do I update an image's docs
- How do I add a new image's docs
- Files related to an image's docs
- Files for main Docs repo
- Scripts unrelated to templates
- Issues and Contributing
How do I update an image's docs
content.md for an image; not the
README.md as it's auto-generated from the contents of the other files in that repo. To see the changes to the
./update.sh myimage from the repo root, but do not add the
README.md changes to your pull request. See also
markdownfmt.sh point below.
After opening your Pull Request the changes will be checked by an automated
markdownfmt.sh before it can be merged. A common issue is incorrect spacing such as with two lines missing an empty line between them (double-spaced).
How do I add a new image's docs
- Create a folder for my image:
- Create a
README-short.txt(required, 100 char max)
- Create a
- Create a
- Create a
- Create a
- Add a
./markdownfmt.sh -l myimageto list any files that are non-compliant to
Any files in the list will result in a failed build during continuous integration.
./markdownfmt.sh -d myimageto see a diff of changes required to pass.
./update.sh myimageto generate
myimage/README.mdfor manual review of the generated copy.
Note: do not actually commit the
README.mdfile; it is automatically generated/committed before being uploaded to Docker Hub.
Files related to an image's docs
This is where all the partial (e.g.
content.md) and generated files (e.g.
README.md) for a given image reside, (e.g.
golang/). It must match the name of the image used in
This file is generated using
update.sh. Do not commit or edit this file; it is regenerated periodically by a bot.
This file contains the main content of your image's long description. The basic parts you should have are a "What Is" section and a "How To" section. The following is a basic layout:
# What is XYZ? // about what the contained software is %%LOGO%% # How to use this image // descriptions and examples of common use cases for the image // make use of subsections as necessary
This file is an optional override of the default
get-help.md. This is the content of the "Where to get help" part of the "Quick reference" at the top of the generated README. We recommend linking to the best places for community support like forums, chat rooms, or mailing lists.
This file should contain the URL to the GitHub repository for the Dockerfiles that become the images. The file should be in a single line ending in a newline with no extraneous whitespace. Only one GitHub repo per image repository is supported. It is used in generating links. Here is an example for
This file should contain a link to the license for the main software in the image. Here is an example for
View [license information](http://golang.org/LICENSE) for the software contained in this image.
Logo for the contained software. While there are not hard rules on formatting, most existing logos are square or landscape and stay within a few hundred pixels of width. Alternatively, a
logo.svg can be used instead, but only one logo file will apply. To use it within
%%LOGO%% as shown above in the basic
The image is automatically scaled to a 120 pixel square for the top of the Docker Hub page and Hub search results.
This file should contain a link to the maintainers of the Dockerfile.
This is the short description for the Docker Hub, limited to 100 characters in a single line.
Go (golang) is a general purpose, higher-level, imperative programming language.
This optional file contains a small, working Compose file for Docker Swarm showing off how to use the image. To use the
%%STACK%% to the
content.md and this will embed the YAML along with a link to directly try it in Play with Docker.
The file must work via
docker stack deploy since that is how Play with Docker will launch it, but it is helpful for users to try locally if it works for
docker-compose as well. Other official images may be referenced within the YAML to demonstrate the functionality of the image, but no images external to the Docker Official Images program may be referenced.
Files for main Docs repo
This is the main script used to generate the
README.md files for each image. The generated file is committed along with the files used to generate it. Accepted arguments are which image(s) you want to update or no arguments to update all of them.
This script assumes
bashbrew is in your
PATH (for scraping relevant tag information from the library manifest file for each repository).
This script is used by
update.sh to create the "Supported tags and respective
Dockerfile links" section of each generated
README.md from the information in the official-images
The scripts and Markdown files in here are used in building an image's
README.md file in combination with its individual files.
Scripts unrelated to templates
This is used to generate a simple
README.md to put in the image's repo. We use this in Git repositories within https://github.com/docker-library to simplify our maintenance, but it is not required for anyone else. The only argument is the name of the image (or repo), like
golang and it then outputs the readme to standard out.
These are used by us to push the actual content of the READMEs to the Docker Hub as special access is required to modify the Hub description contents. The
Dockerfile is used to create a suitable environment for
Issues and Contributing
If you would like to make a new Official Image, be sure to follow the guidelines.
Feel free to make a pull request for fixes and improvements to current documentation. For questions or problems on this repo come talk to us via the
#docker-library IRC channel on Libera.Chat or open up an issue.