<commit_before># Docker Official Images

[![Build Status](https://travis-ci.org/docker-library/official-images.svg?branch=master)](https://travis-ci.org/docker-library/official-images)

## What are "Official Images"?

See [Docker's documentation](https://docs.docker.com/docker-hub/official_repos/) for a good high-level overview of the program.

## Architectures other than amd64?

Work is in-progress in the Docker Engine and Registry to properly support multiple architectures (see [docker/docker#15866](https://github.com/docker/docker/issues/15866)). While this work is ongoing, **temporary**, experimental builds of the official images for the following architectures are happening somewhat incrementally (with a strong bias towards images necessary for Docker's own CI to help hasten proper multiarch support upstream) via CI.

-	ARMv5 (`armel`): https://hub.docker.com/u/armel/
-	ARMv7 (`armhf`): https://hub.docker.com/u/armhf/
-	ARMv8 (`arm64`): https://hub.docker.com/u/aarch64/
-	POWER8 (`ppc64le`): https://hub.docker.com/u/ppc64le/
-	System z (`s390x`): https://hub.docker.com/u/s390x/
-	x86/i686 (`i386`): https://hub.docker.com/u/i386/

If you are curious about how these images are built or have issues with them, please direct all comments to [issues on the `tianon/jenkins-groovy` repo](https://github.com/tianon/jenkins-groovy/issues) for now.

## Contributing to the standard library

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 Freenode IRC in channel `#docker-library` or by creating a GitHub issue here.

Be sure to familiarize yourself with [Official Repositories on Docker Hub](https://docs.docker.com/docker-hub/official_repos/) and the [Best practices for writing Dockerfiles](https://docs.docker.com/articles/dockerfile_best-practices/) in the Docker documentation. These will be the foundation of the review process performed by the official images maintainers. If you'd like the review process to go more smoothly, please ensure that your `Dockerfile`s adhere to all the points mentioned there, as well as [below](README.md#review-guidelines), before submitting a pull request.
<commit_msg>Refactor the "multiarch" section of the README to make it clear these things are now "officially supported" (in many cases)<commit_after># Docker Official Images

[![Build Status](https://travis-ci.org/docker-library/official-images.svg?branch=master)](https://travis-ci.org/docker-library/official-images)

## What are "Official Images"?

See [Docker's documentation](https://docs.docker.com/docker-hub/official_repos/) for a good high-level overview of the program.

## Architectures other than amd64?

Some images have been ported for other architectures, and many of these are officially supported. These are the supported architectures:

-	IBM z Systems (`s390x`): https://hub.docker.com/u/s390x/
-	POWER8 (`ppc64le`): https://hub.docker.com/u/ppc64le/
-	x86/i686 (`i386`): https://hub.docker.com/u/i386/
-	ARMv8 (`arm64v8`): https://hub.docker.com/u/arm64v8/
-	ARMv7 (`arm32v7`): https://hub.docker.com/u/arm32v7/
-	ARMv6 (`arm32v6`): https://hub.docker.com/u/arm32v6/ (Raspberry Pi 1, Raspberry Pi Zero)
-	ARMv5 (`arm32v5`): https://hub.docker.com/u/arm32v5/

Check each image description for individual image support status (for example, https://hub.docker.com/r/s390x/golang/ is officially supported).

If you're curious about how these are built, head over to https://doi-janky.infosiftr.net/job/multiarch/ to see the build scaffolding for these other architectures.

## Contributing to the standard library

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 Freenode IRC in channel `#docker-library` or by creating a GitHub issue here.

Be sure to familiarize yourself with [Official Repositories on Docker Hub](https://docs.docker.com/docker-hub/official_repos/) and the [Best practices for writing Dockerfiles](https://docs.docker.com/articles/dockerfile_best-practices/) in the Docker documentation. These will be the foundation of the review process performed by the official images maintainers. If you'd like the review process to go more smoothly, please ensure that your `Dockerfile`s adhere to all the points mentioned there, as well as [below](README.md#review-guidelines), before submitting a pull request.

{'fraction_non_alphanumeric': 0.10683854052873061, 'fraction_numerical': 0.02119292112737601, 'mean_word_length': 4.831847133757962, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 27, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2690308', 'n_tokens_mistral': 1464, 'n_tokens_neox': 1301, 'n_words': 498}