Run update.sh (arm64v8 -- https://hub.docker.com/u/arm64v8/)

adminer/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `adminer` official image](https://hub.docker.com/_/adminer) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -66,7 +68,7 @@ Adminer (formerly phpMinAdmin) is a full-featured database management tool writt
 ### Standalone
 
 ```console
-$ docker run --link some_database:db -p 8080:8080 adminer
+$ docker run --link some_database:db -p 8080:8080 arm64v8/adminer
 ```
 
 Then you can hit `http://localhost:8080` or `http://host-ip:8080` in your browser.
@@ -76,7 +78,7 @@ Then you can hit `http://localhost:8080` or `http://host-ip:8080` in your browse
 If you are already running a FastCGI capable web server you might prefer running Adminer via FastCGI:
 
 ```console
-$ docker run --link some_database:db -p 9000:9000 adminer:fastcgi
+$ docker run --link some_database:db -p 9000:9000 arm64v8/adminer:fastcgi
 ```
 
 Then point your web server to port 9000 of the container.
@@ -114,13 +116,13 @@ This image bundles all official Adminer plugins. You can find the list of plugin
 To load plugins you can pass a list of filenames in `ADMINER_PLUGINS`:
 
 ```console
-$ docker run --link some_database:db -p 8080:8080 -e ADMINER_PLUGINS='tables-filter tinymce' adminer
+$ docker run --link some_database:db -p 8080:8080 -e ADMINER_PLUGINS='tables-filter tinymce' arm64v8/adminer
 ```
 
 If a plugin *requires* parameters to work correctly instead of adding the plugin to `ADMINER_PLUGINS`, you need to add a custom file to the container:
 
 ```console
-$ docker run --link some_database:db -p 8080:8080 -e ADMINER_PLUGINS='login-servers' adminer
+$ docker run --link some_database:db -p 8080:8080 -e ADMINER_PLUGINS='login-servers' arm64v8/adminer
 Unable to load plugin file "login-servers", because it has required parameters: servers
 Create a file "/var/www/html/plugins-enabled/login-servers.php" with the following contents to load the plugin:
 
@@ -146,7 +148,7 @@ The image bundles all the designs that are available in the source package of ad
 To use a bundled design you can pass its name in `ADMINER_DESIGN`:
 
 ```console
-$ docker run --link some_database:db -p 8080:8080 -e ADMINER_DESIGN='nette' adminer
+$ docker run --link some_database:db -p 8080:8080 -e ADMINER_DESIGN='nette' arm64v8/adminer
 ```
 
 To use a custom design you can add a file called `/var/www/html/adminer.css`.
@@ -156,7 +158,7 @@ To use a custom design you can add a file called `/var/www/html/adminer.css`.
 You can specify the default host with the `ADMINER_DEFAULT_SERVER` environment variable. This is useful if you are connecting to an external server or a docker container named something other than the default `db`.
 
 ```console
-docker run -p 8080:8080 -e ADMINER_DEFAULT_SERVER=mysql adminer
+docker run -p 8080:8080 -e ADMINER_DEFAULT_SERVER=mysql arm64v8/adminer
 ```
 
 ## Supported Drivers

aerospike/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `aerospike` official image](https://hub.docker.com/_/aerospike) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -66,7 +68,7 @@ Aerospike Community Edition supports the same developer APIs as Aerospike Enterp
 ### Running an Aerospike EE node with a feature key file in a mapped directory
 
 ```console
-docker run -d -v DIR:/opt/aerospike/etc/ -e "FEATURE_KEY_FILE=/opt/aerospike/etc/features.conf" --name aerospike -p 3000-3002:3000-3002 aerospike:ee-[version]
+docker run -d -v DIR:/opt/aerospike/etc/ -e "FEATURE_KEY_FILE=/opt/aerospike/etc/features.conf" --name aerospike -p 3000-3002:3000-3002 arm64v8/aerospike:ee-[version]
 ```
 
 Above, *DIR* is a directory on your machine where you drop your feature key file. Make sure Docker Desktop has file sharing permission to bind mount it into Docker containers.
@@ -75,13 +77,13 @@ Above, *DIR* is a directory on your machine where you drop your feature key file
 
 ```console
 FEATKEY=$(base64 ~/Desktop/evaluation-features.conf)
-docker run -d -e "FEATURES=$FEATKEY" -e "FEATURE_KEY_FILE=env-b64:FEATURES" --name aerospike -p 3000-3002:3000-3002 aerospike:ee-[version]
+docker run -d -e "FEATURES=$FEATKEY" -e "FEATURE_KEY_FILE=env-b64:FEATURES" --name aerospike -p 3000-3002:3000-3002 arm64v8/aerospike:ee-[version]
 ```
 
 ### Running an Aerospike CE node
 
 ```console
-docker run -d --name aerospike -p 3000-3002:3000-3002 aerospike:ce-[version]
+docker run -d --name aerospike -p 3000-3002:3000-3002 arm64v8/aerospike:ce-[version]
 ```
 
 ## Advanced Configuration
@@ -97,7 +99,7 @@ You can inject parameters into the configuration template using container-side e
 For example, to set the default [namespace](https://www.aerospike.com/docs/architecture/data-model.html) name to *demo*:
 
 ```console
-docker run -d --name aerospike -e "NAMESPACE=demo" -p 3000-3002:3000-3002 -v /my/dir:/opt/aerospike/etc/ -e "FEATURE_KEY_FILE=/opt/aerospike/etc/features.conf" aerospike:ee-[version]
+docker run -d --name aerospike -e "NAMESPACE=demo" -p 3000-3002:3000-3002 -v /my/dir:/opt/aerospike/etc/ -e "FEATURE_KEY_FILE=/opt/aerospike/etc/features.conf" arm64v8/aerospike:ee-[version]
 ```
 
 Injecting configuration parameters into the configuration template isn't compatible with using a custom configuration file. You can use one or the other.
@@ -132,7 +134,7 @@ You should first `-v` map a local directory, which Docker will bind mount. Next,
 For example:
 
 ```console
-docker run -d -v /opt/aerospike/etc/:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 aerospike:ee-[version] --config-file /opt/aerospike/etc/aerospike.conf
+docker run -d -v /opt/aerospike/etc/:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 arm64v8/aerospike:ee-[version] --config-file /opt/aerospike/etc/aerospike.conf
 ```
 
 ### Persistent Data Directory
@@ -142,7 +144,7 @@ With Docker, the files within the container are not persisted past the life of t
 For example:
 
 ```console
-docker run -d  -v /opt/aerospike/data:/opt/aerospike/data  -v /opt/aerospike/etc:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 -e "FEATURE_KEY_FILE=/opt/aerospike/etc/features.conf" aerospike:ee-[version]
+docker run -d  -v /opt/aerospike/data:/opt/aerospike/data  -v /opt/aerospike/etc:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 -e "FEATURE_KEY_FILE=/opt/aerospike/etc/features.conf" arm64v8/aerospike:ee-[version]
 ```
 
 The example above uses the configuration template, where the single defined namespace is in-memory with file-based persistence. Just mounting the predefined /opt/aerospike/data directory enables the data to be persisted on the host.
@@ -161,7 +163,7 @@ Alternatively, a custom configuration file is used with the parameter `file` set
 In this example we also mount the data directory in a similar way, using a custom configuration file.
 
 ```console
-docker run -d -v /opt/aerospike/data:/opt/aerospike/data -v /opt/aerospike/etc/:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 aerospike:ee-[version] --config-file /opt/aerospike/etc/aerospike.conf
+docker run -d -v /opt/aerospike/data:/opt/aerospike/data -v /opt/aerospike/etc/:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 arm64v8/aerospike:ee-[version] --config-file /opt/aerospike/etc/aerospike.conf
 ```
 
 ### Block Storage
@@ -181,7 +183,7 @@ Update the `storage-engine device` section of the namespace in the custom aerosp
 Now to map a host drive /dev/sdc to /dev/xvdc on a container
 
 ```console
-docker run -d --device '/dev/sdc:/dev/xvdc' -v /opt/aerospike/etc/:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 aerospike:ee-[version] --config-file /opt/aerospike/etc/aerospike.conf
+docker run -d --device '/dev/sdc:/dev/xvdc' -v /opt/aerospike/etc/:/opt/aerospike/etc/ --name aerospike -p 3000-3002:3000-3002 arm64v8/aerospike:ee-[version] --config-file /opt/aerospike/etc/aerospike.conf
 ```
 
 ### Persistent Lua Cache
@@ -189,7 +191,7 @@ docker run -d --device '/dev/sdc:/dev/xvdc' -v /opt/aerospike/etc/:/opt/aerospik
 Upon restart, your lua cache will become emptied. To persist the cache, you will want to mount a directory from the host to the container's `/opt/aerospike/usr/udf/lua` using the `-v` option:
 
 ```sh
-docker run -d -v /opt/aerospike/lua:/opt/aerospike/usr/udf/lua -v /opt/aerospike/data:/opt/aerospike/data --name aerospike -p 3000-3002:3000-3002 -e "FEATURE_KEY_FILE=/opt/etc/aerospike/features.conf" aerospike:ee-[version]
+docker run -d -v /opt/aerospike/lua:/opt/aerospike/usr/udf/lua -v /opt/aerospike/data:/opt/aerospike/data --name aerospike -p 3000-3002:3000-3002 -e "FEATURE_KEY_FILE=/opt/etc/aerospike/features.conf" arm64v8/aerospike:ee-[version]
 ```
 
 ## Clustering

almalinux/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `almalinux` official image](https://hub.docker.com/_/almalinux) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,21 +26,21 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`10-kitten`, `10-kitten-20250909`](https://github.com/AlmaLinux/container-images/blob/571a3caca09a9dd0f8c81c7834af79b8f9ad8ab2/default/amd64/Dockerfile)
+-	[`10-kitten`, `10-kitten-20250909`](https://github.com/AlmaLinux/container-images/blob/571a3caca09a9dd0f8c81c7834af79b8f9ad8ab2/default/arm64/Dockerfile)
 
--	[`10-kitten-minimal`, `10-kitten-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/571a3caca09a9dd0f8c81c7834af79b8f9ad8ab2/minimal/amd64/Dockerfile)
+-	[`10-kitten-minimal`, `10-kitten-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/571a3caca09a9dd0f8c81c7834af79b8f9ad8ab2/minimal/arm64/Dockerfile)
 
--	[`10`, `10.0`, `10.0-20250909`](https://github.com/AlmaLinux/container-images/blob/2f239bc800a366ea4dc42378905c237ae6e4e03a/default/amd64/Dockerfile)
+-	[`10`, `10.0`, `10.0-20250909`](https://github.com/AlmaLinux/container-images/blob/2f239bc800a366ea4dc42378905c237ae6e4e03a/default/arm64/Dockerfile)
 
--	[`10-minimal`, `10.0-minimal`, `10.0-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/2f239bc800a366ea4dc42378905c237ae6e4e03a/minimal/amd64/Dockerfile)
+-	[`10-minimal`, `10.0-minimal`, `10.0-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/2f239bc800a366ea4dc42378905c237ae6e4e03a/minimal/arm64/Dockerfile)
 
--	[`8`, `8.10`, `8.10-20250909`](https://github.com/AlmaLinux/container-images/blob/1bee999abd112c603a3044f96282a2c1b66cb57f/default/amd64/Dockerfile)
+-	[`8`, `8.10`, `8.10-20250909`](https://github.com/AlmaLinux/container-images/blob/1bee999abd112c603a3044f96282a2c1b66cb57f/default/arm64/Dockerfile)
 
--	[`8-minimal`, `8.10-minimal`, `8.10-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/1bee999abd112c603a3044f96282a2c1b66cb57f/minimal/amd64/Dockerfile)
+-	[`8-minimal`, `8.10-minimal`, `8.10-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/1bee999abd112c603a3044f96282a2c1b66cb57f/minimal/arm64/Dockerfile)
 
--	[`latest`, `9`, `9.6`, `9.6-20250909`](https://github.com/AlmaLinux/container-images/blob/17f5f89c183962069c90892cd92c8b83598b8807/default/amd64/Dockerfile)
+-	[`latest`, `9`, `9.6`, `9.6-20250909`](https://github.com/AlmaLinux/container-images/blob/17f5f89c183962069c90892cd92c8b83598b8807/default/arm64/Dockerfile)
 
--	[`minimal`, `9-minimal`, `9.6-minimal`, `9.6-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/17f5f89c183962069c90892cd92c8b83598b8807/minimal/amd64/Dockerfile)
+-	[`minimal`, `9-minimal`, `9.6-minimal`, `9.6-minimal-20250909`](https://github.com/AlmaLinux/container-images/blob/17f5f89c183962069c90892cd92c8b83598b8807/minimal/arm64/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -71,13 +73,13 @@ WARNING:
 
 The default (platform) image is a general-purpose image with a full DNF stack and basic tools like find, tar, vi, etc.
 
-The `almalinux:latest` tag will always point to the latest stable release of the default image. Major releases and minor releases are also tagged with their version (e.g. `almalinux:8` or `almalinux:8.4`).
+The `arm64v8/almalinux:latest` tag will always point to the latest stable release of the default image. Major releases and minor releases are also tagged with their version (e.g. `arm64v8/almalinux:8` or `arm64v8/almalinux:8.4`).
 
 ## Minimal image
 
 The minimal image is a stripped-down image that uses the microdnf package manager and contains a very limited package set. It is designed for applications that come with their own dependencies bundled (e.g. NodeJS, Python).
 
-The `almalinux:minimal` tag always points to the most recent version of the minimal image. Tags for major (e.g. `almalinux:8-minimal`) and minor (e.g. `almalinux:8.4-minimal`) releases are also available.
+The `arm64v8/almalinux:minimal` tag always points to the most recent version of the minimal image. Tags for major (e.g. `arm64v8/almalinux:8-minimal`) and minor (e.g. `arm64v8/almalinux:8.4-minimal`) releases are also available.
 
 ### Upgrade policy
 

alpine/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `alpine` official image](https://hub.docker.com/_/alpine) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,15 +26,15 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`20250108`, `edge`](https://github.com/alpinelinux/docker-alpine/blob/c1f1de232c970df2285c03050ab3747b8563164f/x86_64/Dockerfile)
+-	[`20250108`, `edge`](https://github.com/alpinelinux/docker-alpine/blob/c1f1de232c970df2285c03050ab3747b8563164f/aarch64/Dockerfile)
 
--	[`3.22.2`, `3.22`, `3`, `latest`](https://github.com/alpinelinux/docker-alpine/blob/4dc13cbc7caffe03c98aa99f28e27c2fb6f7e74d/x86_64/Dockerfile)
+-	[`3.22.2`, `3.22`, `3`, `latest`](https://github.com/alpinelinux/docker-alpine/blob/4dc13cbc7caffe03c98aa99f28e27c2fb6f7e74d/aarch64/Dockerfile)
 
--	[`3.21.5`, `3.21`](https://github.com/alpinelinux/docker-alpine/blob/2c30d5daeebb5090b1b6363a9e97dd88bf08a642/x86_64/Dockerfile)
+-	[`3.21.5`, `3.21`](https://github.com/alpinelinux/docker-alpine/blob/2c30d5daeebb5090b1b6363a9e97dd88bf08a642/aarch64/Dockerfile)
 
--	[`3.20.8`, `3.20`](https://github.com/alpinelinux/docker-alpine/blob/f5ce8f036ef8a57481ae6f3f1cf7f2300cff8d29/x86_64/Dockerfile)
+-	[`3.20.8`, `3.20`](https://github.com/alpinelinux/docker-alpine/blob/f5ce8f036ef8a57481ae6f3f1cf7f2300cff8d29/aarch64/Dockerfile)
 
--	[`3.19.9`, `3.19`](https://github.com/alpinelinux/docker-alpine/blob/ee939d52345248420cf62d4606ccc7152bc5a107/x86_64/Dockerfile)
+-	[`3.19.9`, `3.19`](https://github.com/alpinelinux/docker-alpine/blob/ee939d52345248420cf62d4606ccc7152bc5a107/aarch64/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -66,7 +68,7 @@ WARNING:
 Use like you would any other base image:
 
 ```dockerfile
-FROM alpine:3.14
+FROM arm64v8/alpine:3.14
 RUN apk add --no-cache mysql-client
 ENTRYPOINT ["mysql"]
 ```

alt/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `alt` official image](https://hub.docker.com/_/alt) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,11 +26,11 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`p10`](https://github.com/alt-cloud/docker-brew-alt/blob/ef522411b7245d758aa8c8a24a0575c742fac1a2/x86_64/Dockerfile)
+-	[`p10`](https://github.com/alt-cloud/docker-brew-alt/blob/ef522411b7245d758aa8c8a24a0575c742fac1a2/aarch64/Dockerfile)
 
--	[`sisyphus`](https://github.com/alt-cloud/docker-brew-alt/blob/f6fcb549885ee57d7bbb53a22484ee16cb9413b0/x86_64/Dockerfile)
+-	[`sisyphus`](https://github.com/alt-cloud/docker-brew-alt/blob/f6fcb549885ee57d7bbb53a22484ee16cb9413b0/aarch64/Dockerfile)
 
--	[`p11`, `latest`](https://github.com/alt-cloud/docker-brew-alt/blob/068702e0e800b291f7853380450a5557e56900c3/x86_64/Dockerfile)
+-	[`p11`, `latest`](https://github.com/alt-cloud/docker-brew-alt/blob/068702e0e800b291f7853380450a5557e56900c3/aarch64/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -73,7 +75,7 @@ As said above, Sisyphus is a frequently updated repository mainly designed for d
 
 # About this image
 
-The `alt:latest` tag will always point the latest stable release (which is, at the time of this writing, `alt:p9`).
+The `arm64v8/alt:latest` tag will always point the latest stable release (which is, at the time of this writing, `arm64v8/alt:p9`).
 
 ## How It's Made
 

amazoncorretto/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `amazoncorretto` official image](https://hub.docker.com/_/amazoncorretto) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -197,13 +199,13 @@ Note that there are multiple reasons why a CVE may appear to be present in a doc
 
 # Image Variants
 
-The `amazoncorretto` images come in many flavors, each designed for a specific use case.
+The `arm64v8/amazoncorretto` images come in many flavors, each designed for a specific use case.
 
-## `amazoncorretto:<version>`
+## `arm64v8/amazoncorretto:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `amazoncorretto:<version>-alpine`
+## `arm64v8/amazoncorretto:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

amazonlinux/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `amazonlinux` official image](https://hub.docker.com/_/amazonlinux) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,11 +26,9 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`2023`, `latest`, `2023.9.20250929.0`](https://github.com/amazonlinux/container-images/blob/929de1dd8d1747a34701660136a6654d5ef312cc/Dockerfile)
-
--	[`2`, `2.0.20250929.2`](https://github.com/amazonlinux/container-images/blob/bd6f28b0f4dac5ef4dadc1e141d005d65ef60be1/Dockerfile)
+-	[`2023`, `latest`, `2023.9.20250929.0`](https://github.com/amazonlinux/container-images/blob/b5c8d4d3115e5985262be7fc9ef69cd89b208e25/Dockerfile)
 
--	[`1`, `2018.03`, `2018.03.0.20231218.0`](https://github.com/amazonlinux/container-images/blob/cfb41ad1c7624786ea10f60c15ce9c117c4da3b6/Dockerfile)
+-	[`2`, `2.0.20250929.2`](https://github.com/amazonlinux/container-images/blob/b71f2b91c30d85b457f99c5073adc7a5a61370c0/Dockerfile)
 
 # Quick reference (cont.)
 

api-firewall/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `api-firewall` official image](https://hub.docker.com/_/api-firewall) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

arangodb/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `arangodb` official image](https://hub.docker.com/_/arangodb) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -75,16 +77,16 @@ ArangoDB runs everywhere: On-prem, in the cloud, and as a managed cloud service:
 In order to start an ArangoDB instance, run:
 
 ```console
-docker run -d -p 8529:8529 -e ARANGO_RANDOM_ROOT_PASSWORD=1 --name arangodb-instance arangodb
+docker run -d -p 8529:8529 -e ARANGO_RANDOM_ROOT_PASSWORD=1 --name arangodb-instance arm64v8/arangodb
 ```
 
 Docker chooses the processor architecture for the image that matches your host CPU by default. If this is not the case, for example, because you have the `DOCKER_DEFAULT_PLATFORM` environment variable set to a different architecture, you can pass the `--platform` flag to the `docker run` command to specify the appropriate operating system and architecture for the container. For x86-64, use `linux/amd64`. On ARM, especially Apple silicon with no emulation for the required AVX instruction set extension, use `linux/arm64/v8`:
 
 ```console
-docker run -d -p 8529:8529 -e ARANGO_RANDOM_ROOT_PASSWORD=1 --name arangodb-instance --platform linux/arm64/v8 arangodb
+docker run -d -p 8529:8529 -e ARANGO_RANDOM_ROOT_PASSWORD=1 --name arangodb-instance --platform linux/arm64/v8 arm64v8/arangodb
 ```
 
-This creates and launches the arangodb Docker instance as a background process. The Identifier of the process is printed. By default, ArangoDB listens on port `8529` for requests.
+This creates and launches the arm64v8/arangodb Docker instance as a background process. The Identifier of the process is printed. By default, ArangoDB listens on port `8529` for requests.
 
 In order to get the IP ArangoDB listens on, run:
 
@@ -107,7 +109,7 @@ If you don't specify a language explicitly, the default is `en_US` up to ArangoD
 To use the running instance from an application, link the container:
 
 ```console
-docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 --name my-app --link arangodb-instance:db-link arangodb
+docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 --name my-app --link arangodb-instance:db-link arm64v8/arangodb
 ```
 
 This uses the instance named `arangodb-instance` and links it into the application container. The application container contains environment variables, which can be used to access the database.
@@ -123,7 +125,7 @@ This uses the instance named `arangodb-instance` and links it into the applicati
 If you want to expose the port to the outside world, run:
 
 ```console
-docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 -p 8529:8529 -d arangodb
+docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 -p 8529:8529 -d arm64v8/arangodb
 ```
 
 ArangoDB listen on port 8529 for request and the image includes `EXPOSE
@@ -154,7 +156,7 @@ Note: this way of specifying logins only applies to single server installations.
 You can pass arguments to the ArangoDB server by appending them to the end of the Docker command:
 
 ```console
-docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 arangodb --help
+docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 arm64v8/arangodb --help
 ```
 
 The entrypoint script starts the `arangod` binary by default and forwards your arguments.
@@ -162,7 +164,7 @@ The entrypoint script starts the `arangod` binary by default and forwards your a
 You may also start other binaries, such as the ArangoShell:
 
 ```console
-docker run -it arangodb arangosh --server.database myDB ...
+docker run -it arm64v8/arangodb arangosh --server.database myDB ...
 ```
 
 Note that you need to set up networking for containers if `arangod` runs in one container and you want to access it with `arangosh` running in another container. It is easier to execute it in the same container instead. Use `docker ps` to find out the container ID / name of a running container:
@@ -215,7 +217,7 @@ ArangoDB supports two different storage engines from version 3.2 to 3.6. You can
 
 ArangoDB uses the volume `/var/lib/arangodb3` as database directory to store the collection data and the volume `/var/lib/arangodb3-apps` as apps directory to store any extensions. These directories are marked as docker volumes.
 
-See `docker inspect --format "{{ .Config.Volumes }}" arangodb` for all volumes.
+See `docker inspect --format "{{ .Config.Volumes }}" arm64v8/arangodb` for all volumes.
 
 A good explanation about persistence and docker container can be found here: [Docker In-depth: Volumes](http://container42.com/2014/11/03/docker-indepth-volumes/), [Why Docker Data Containers are Good](https://medium.com/@ramangupta/why-docker-data-containers-are-good-589b3c6c749e)
 
@@ -227,7 +229,7 @@ You can map the container's volumes to a directory on the host, so that the data
 unix> mkdir /tmp/arangodb
 unix> docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 -p 8529:8529 -d \
         -v /tmp/arangodb:/var/lib/arangodb3 \
-        arangodb
+        arm64v8/arangodb
 ```
 
 This will use the `/tmp/arangodb` directory of the host as database directory for ArangoDB inside the container.
@@ -237,13 +239,13 @@ This will use the `/tmp/arangodb` directory of the host as database directory fo
 Alternatively you can create a container holding the data.
 
 ```console
-docker create --name arangodb-persist arangodb true
+docker create --name arangodb-persist arm64v8/arangodb true
 ```
 
 And use this data container in your ArangoDB container.
 
 ```console
-docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 --volumes-from arangodb-persist -p 8529:8529 arangodb
+docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 --volumes-from arangodb-persist -p 8529:8529 arm64v8/arangodb
 ```
 
 If want to save a few bytes you can alternatively use [busybox](https://hub.docker.com/_/busybox) or [alpine](https://hub.docker.com/_/alpine) for creating the volume only containers. Please note that you need to provide the used volumes in this case. For example

archlinux/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `archlinux` official image](https://hub.docker.com/_/archlinux) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,11 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`latest`, `base`, `base-20251019.0.436919`](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/blob/3d3996ec400b3b9ef1c04fa5b4b6b81725a8eaac/Dockerfile.base)
-
--	[`base-devel`, `base-devel-20251019.0.436919`](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/blob/3d3996ec400b3b9ef1c04fa5b4b6b81725a8eaac/Dockerfile.base-devel)
-
--	[`multilib-devel`, `multilib-devel-20251019.0.436919`](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/blob/3d3996ec400b3b9ef1c04fa5b4b6b81725a8eaac/Dockerfile.multilib-devel)
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -61,7 +59,7 @@ Our strong community is diverse and helpful, and we pride ourselves on the range
 
 # About this image
 
-The root filesystem tarball for this image is auto-generated weekly at 00:00 UTC on Sunday in Arch Linux infrastructure. Given the rolling-release nature of Arch Linux, images are tagged with the included meta package and the timestamp of the date they were generated. For example, `archlinux:base-20201101.0.7893` was generated the First of November 2020 in [CI job #7893](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/jobs/7893). The `latest` tag will always match the latest `base` tag.
+The root filesystem tarball for this image is auto-generated weekly at 00:00 UTC on Sunday in Arch Linux infrastructure. Given the rolling-release nature of Arch Linux, images are tagged with the included meta package and the timestamp of the date they were generated. For example, `arm64v8/archlinux:base-20201101.0.7893` was generated the First of November 2020 in [CI job #7893](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/jobs/7893). The `latest` tag will always match the latest `base` tag.
 
 Besides `base` we also provide images for the `base-devel` and `multilib-devel` meta packages.
 

backdrop/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `backdrop` official image](https://hub.docker.com/_/backdrop) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -60,7 +62,7 @@ Backdrop CMS enables people to build highly customized websites, affordably, thr
 The basic pattern for starting a `backdrop` instance is:
 
 ```console
-$ docker run --name some-backdrop --link some-mysql:mysql -d backdrop
+$ docker run --name some-backdrop --link some-mysql:mysql -d arm64v8/backdrop
 ```
 
 The following environment variables are also honored for configuring your Backdrop CMS instance:
@@ -77,7 +79,7 @@ The `BACKDROP_DB_NAME` **must already exist** on the given MySQL server. Check o
 If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:
 
 ```console
-$ docker run --name some-backdrop --link some-mysql:mysql -p 8080:80 -d backdrop
+$ docker run --name some-backdrop --link some-mysql:mysql -p 8080:80 -d arm64v8/backdrop
 ```
 
 Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browser.

bash/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `bash` official image](https://hub.docker.com/_/bash) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -92,7 +94,7 @@ There are a few main things that are important to note regarding this image:
 ## Interactive shell
 
 ```console
-$ docker run -it --rm bash:4.4
+$ docker run -it --rm arm64v8/bash:4.4
 bash-4.4# which bash
 /usr/local/bin/bash
 bash-4.4# echo $BASH_VERSION
@@ -102,16 +104,16 @@ bash-4.4# echo $BASH_VERSION
 ## Testing scripts via bind-mount
 
 ```console
-$ docker run -it --rm -v /path/to/script.sh:/script.sh:ro bash:4.4 bash /script.sh
+$ docker run -it --rm -v /path/to/script.sh:/script.sh:ro arm64v8/bash:4.4 bash /script.sh
 ...
-$ docker run -it --rm -v /path/to/script.sh:/script.sh:ro bash:3.2 bash /script.sh
+$ docker run -it --rm -v /path/to/script.sh:/script.sh:ro arm64v8/bash:3.2 bash /script.sh
 ...
 ```
 
 ## Testing scripts via `Dockerfile`
 
 ```dockerfile
-FROM bash:4.4
+FROM arm64v8/bash:4.4
 
 COPY script.sh /
 

bonita/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `bonita` official image](https://hub.docker.com/_/bonita) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,7 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`2025.1-u0`, `2025.1`, `10.3.0`, `10.3`, `latest`](https://github.com/bonitasoft/bonita-distrib/blob/adca7d9251091cd02f3cde7c0a9cee0e1538c7a1/docker/Dockerfile)
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -58,7 +60,7 @@ Bonita is an open-source business process management and workflow suite created
 ## Quick start
 
 ```console
-$ docker run --name bonita -d -p 8080:8080 bonita
+$ docker run --name bonita -d -p 8080:8080 arm64v8/bonita
 ```
 
 This will start a container running [Bonita runtime](https://documentation.bonitasoft.com/bonita/latest/tomcat-bundle): a Tomcat bundle with Bonita Engine + Bonita Portal. With no environment variables specified, it's as if you have launched the bundle on your host using startup.{sh|bat} (with security hardening on REST and HTTP APIs, cf Security part). Bonita uses a H2 database here.
@@ -143,13 +145,13 @@ BIZ_DB_PASS=custombusinesspass
 ```
 
 ```bash
-docker run --name=bonita -h <hostname> --env-file=env.txt -d -p 8080:8080 bonita
+docker run --name=bonita -h <hostname> --env-file=env.txt -d -p 8080:8080 arm64v8/bonita
 ```
 
 ## Start Bonita with custom security credentials
 
 ```bash
-docker run --name=bonita -h <hostname> -e "BONITA_RUNTIME_ADMIN_USERNAME=tech_user" -e "BONITA_RUNTIME_ADMIN_PASSWORD=secret" -e "PLATFORM_LOGIN=pfadmin" -e "PLATFORM_PASSWORD=pfsecret" -d -p 8080:8080 bonita
+docker run --name=bonita -h <hostname> -e "BONITA_RUNTIME_ADMIN_USERNAME=tech_user" -e "BONITA_RUNTIME_ADMIN_PASSWORD=secret" -e "PLATFORM_LOGIN=pfadmin" -e "PLATFORM_PASSWORD=pfsecret" -d -p 8080:8080 arm64v8/bonita
 ```
 
 Now you can access the Bonita Runtime on localhost:8080/bonita and login using: tech_user / secret
@@ -290,7 +292,7 @@ This Docker image activates both static and dynamic authorization checks by defa
 For specific needs you can override this behavior by setting HTTP_API to true:
 
 ```console
-$ docker run  -e HTTP_API=true -e HTTP_API_PASSWORD="My-Cust0m_S3cR3T" --name bonita -d -p 8080:8080 bonita
+$ docker run  -e HTTP_API=true -e HTTP_API_PASSWORD="My-Cust0m_S3cR3T" --name bonita -d -p 8080:8080 arm64v8/bonita
 ```
 
 ## Update from an earlier version of Bonita
@@ -367,7 +369,7 @@ For updating from a version before 7.10.0, please refer to the [documentation](h
 -	Launch the new container pointing towards the copy of the database.
 
 	```console
-	$ docker run --name=bonita --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 bonita:2025.1-u0
+	$ docker run --name=bonita --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 arm64v8/bonita:2025.1-u0
 	```
 
 For more details regarding Bonita update and for version before 7.10.0, see the [documentation](https://documentation.bonitasoft.com/bonita/latest/version-update/migrate-from-an-earlier-version-of-bonita).

buildpack-deps/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `buildpack-deps` official image](https://hub.docker.com/_/buildpack-deps) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

busybox/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `busybox` official image](https://hub.docker.com/_/busybox) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,21 +26,21 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`1.37.0-glibc`, `1.37-glibc`, `1-glibc`, `unstable-glibc`, `glibc`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest/glibc/amd64/index.json)
+-	[`1.37.0-glibc`, `1.37-glibc`, `1-glibc`, `unstable-glibc`, `glibc`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest/glibc/arm64v8/index.json)
 
--	[`1.37.0-uclibc`, `1.37-uclibc`, `1-uclibc`, `unstable-uclibc`, `uclibc`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest/uclibc/amd64/index.json)
+-	[`1.37.0-uclibc`, `1.37-uclibc`, `1-uclibc`, `unstable-uclibc`, `uclibc`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest/uclibc/arm64v8/index.json)
 
--	[`1.37.0-musl`, `1.37-musl`, `1-musl`, `unstable-musl`, `musl`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest/musl/amd64/index.json)
+-	[`1.37.0-musl`, `1.37-musl`, `1-musl`, `unstable-musl`, `musl`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest/musl/arm64v8/index.json)
 
--	[`1.37.0`, `1.37`, `1`, `unstable`, `latest`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest/glibc/amd64/index.json)
+-	[`1.37.0`, `1.37`, `1`, `unstable`, `latest`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest/glibc/arm64v8/index.json)
 
--	[`1.36.1-glibc`, `1.36-glibc`, `stable-glibc`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest-1/glibc/amd64/index.json)
+-	[`1.36.1-glibc`, `1.36-glibc`, `stable-glibc`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest-1/glibc/arm64v8/index.json)
 
--	[`1.36.1-uclibc`, `1.36-uclibc`, `stable-uclibc`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest-1/uclibc/amd64/index.json)
+-	[`1.36.1-uclibc`, `1.36-uclibc`, `stable-uclibc`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest-1/uclibc/arm64v8/index.json)
 
--	[`1.36.1-musl`, `1.36-musl`, `stable-musl`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest-1/musl/amd64/index.json)
+-	[`1.36.1-musl`, `1.36-musl`, `stable-musl`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest-1/musl/arm64v8/index.json)
 
--	[`1.36.1`, `1.36`, `stable`](https://github.com/docker-library/busybox/blob/e5b5178110ca0332364a77d5eb4fff87b0e2ba3f/latest-1/glibc/amd64/index.json)
+-	[`1.36.1`, `1.36`, `stable`](https://github.com/docker-library/busybox/blob/f30de561de9bf38da10058620e9c4c383ec8a905/latest-1/glibc/arm64v8/index.json)
 
 # Quick reference (cont.)
 
@@ -74,7 +76,7 @@ BusyBox combines tiny versions of many common UNIX utilities into a single small
 ## Run BusyBox shell
 
 ```console
-$ docker run -it --rm busybox
+$ docker run -it --rm arm64v8/busybox
 ```
 
 This will drop you into an `sh` shell to allow you to do what you want inside a BusyBox system.
@@ -82,7 +84,7 @@ This will drop you into an `sh` shell to allow you to do what you want inside a
 ## Create a `Dockerfile` for a binary
 
 ```dockerfile
-FROM busybox
+FROM arm64v8/busybox
 COPY ./my-static-binary /my-static-binary
 CMD ["/my-static-binary"]
 ```
@@ -91,19 +93,19 @@ This `Dockerfile` will allow you to create a minimal image for your statically c
 
 # Image Variants
 
-The `busybox` images contain BusyBox built against various "libc" variants (for a comparison of "libc" variants, [Eta Labs has a very nice chart](http://www.etalabs.net/compare_libcs.html) which lists many similarities and differences).
+The `arm64v8/busybox` images contain BusyBox built against various "libc" variants (for a comparison of "libc" variants, [Eta Labs has a very nice chart](http://www.etalabs.net/compare_libcs.html) which lists many similarities and differences).
 
 For more information about the specific particulars of the build process for each variant, see `Dockerfile.builder` in the same directory as each variant's `Dockerfile` (see links above).
 
-## `busybox:glibc`
+## `arm64v8/busybox:glibc`
 
 -	[glibc from Debian](https://packages.debian.org/search?searchon=names&exact=1&suite=all&section=all&keywords=libc6) (which is then included in the image)
 
-## `busybox:uclibc`
+## `arm64v8/busybox:uclibc`
 
 -	[uClibc](https://uclibc.org) via [Buildroot](https://buildroot.org) (statically compiled)
 
-## `busybox:musl`
+## `arm64v8/busybox:musl`
 
 -	[musl from Alpine](https://pkgs.alpinelinux.org/packages?name=musl) (statically compiled)
 

caddy/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `caddy` official image](https://hub.docker.com/_/caddy) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -32,32 +34,15 @@ WARNING:
 
 -	[`2.10.2-builder-alpine`, `2.10-builder-alpine`, `2-builder-alpine`, `builder-alpine`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/builder/Dockerfile)
 
--	[`2.10.2-windowsservercore-ltsc2022`, `2.10-windowsservercore-ltsc2022`, `2-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows/ltsc2022/Dockerfile)
-
--	[`2.10.2-windowsservercore-ltsc2025`, `2.10-windowsservercore-ltsc2025`, `2-windowsservercore-ltsc2025`, `windowsservercore-ltsc2025`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows/ltsc2025/Dockerfile)
-
--	[`2.10.2-builder-windowsservercore-ltsc2022`, `2.10-builder-windowsservercore-ltsc2022`, `2-builder-windowsservercore-ltsc2022`, `builder-windowsservercore-ltsc2022`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows-builder/ltsc2022/Dockerfile)
-
--	[`2.10.2-builder-windowsservercore-ltsc2025`, `2.10-builder-windowsservercore-ltsc2025`, `2-builder-windowsservercore-ltsc2025`, `builder-windowsservercore-ltsc2025`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows-builder/ltsc2025/Dockerfile)
-
 ## Shared Tags
 
 -	`2.10.2`, `2.10`, `2`, `latest`:
 
 	-	[`2.10.2-alpine`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/alpine/Dockerfile)
-	-	[`2.10.2-windowsservercore-ltsc2022`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows/ltsc2022/Dockerfile)
-	-	[`2.10.2-windowsservercore-ltsc2025`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows/ltsc2025/Dockerfile)
 
 -	`2.10.2-builder`, `2.10-builder`, `2-builder`, `builder`:
 
 	-	[`2.10.2-builder-alpine`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/builder/Dockerfile)
-	-	[`2.10.2-builder-windowsservercore-ltsc2022`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows-builder/ltsc2022/Dockerfile)
-	-	[`2.10.2-builder-windowsservercore-ltsc2025`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows-builder/ltsc2025/Dockerfile)
-
--	`2.10.2-windowsservercore`, `2.10-windowsservercore`, `2-windowsservercore`, `windowsservercore`:
-
-	-	[`2.10.2-windowsservercore-ltsc2022`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows/ltsc2022/Dockerfile)
-	-	[`2.10.2-windowsservercore-ltsc2025`](https://github.com/caddyserver/caddy-docker/blob/5572371a83e48fd0368a4917d0fc48e44ef30582/2.10/windows/ltsc2025/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -109,7 +94,7 @@ $ echo "hello world" > index.html
 $ docker run -d -p 80:80 \
     -v $PWD/index.html:/usr/share/caddy/index.html \
     -v caddy_data:/data \
-    caddy
+    arm64v8/caddy
 ...
 $ curl http://localhost/
 hello world
@@ -121,7 +106,7 @@ To override the default [`Caddyfile`](https://github.com/caddyserver/dist/blob/m
 $ docker run -d -p 80:80 \
     -v $PWD/conf:/etc/caddy \
     -v caddy_data:/data \
-    caddy
+    arm64v8/caddy
 ```
 
 #### ⚠️ Do not mount the Caddyfile directly at `/etc/caddy/Caddyfile`
@@ -137,7 +122,7 @@ $ docker run -d --cap-add=NET_ADMIN -p 80:80 -p 443:443 -p 443:443/udp \
     -v /site:/srv \
     -v caddy_data:/data \
     -v caddy_config:/config \
-    caddy caddy file-server --domain example.com
+    arm64v8/caddy caddy file-server --domain example.com
 ```
 
 The key here is that Caddy is able to listen to ports `80` and `443`, both required for the ACME HTTP challenge.
@@ -146,11 +131,11 @@ See [Caddy's docs](https://caddyserver.com/docs/automatic-https) for more inform
 
 ### Building your own Caddy-based image
 
-Most users deploying production sites will not want to rely on mounting files into a container, but will instead base their own images on `caddy`:
+Most users deploying production sites will not want to rely on mounting files into a container, but will instead base their own images on `arm64v8/caddy`:
 
 ```Dockerfile
 # note: never use the :latest tag in a production site
-FROM caddy:<version>
+FROM arm64v8/caddy:<version>
 
 COPY Caddyfile /etc/caddy/Caddyfile
 COPY site /srv
@@ -163,18 +148,18 @@ Caddy is extendable through the use of "modules". See https://caddyserver.com/do
 You can use the `:builder` image as a short-cut to building a new Caddy binary:
 
 ```Dockerfile
-FROM caddy:<version>-builder AS builder
+FROM arm64v8/caddy:<version>-builder AS builder
 
 RUN xcaddy build \
     --with github.com/caddyserver/nginx-adapter \
     --with github.com/hairyhenderson/[email protected]
 
-FROM caddy:<version>
+FROM arm64v8/caddy:<version>
 
 COPY --from=builder /usr/bin/caddy /usr/bin/caddy
 ```
 
-Note the second `FROM` instruction - this produces a much smaller image by simply overlaying the newly-built binary on top of the regular `caddy` image.
+Note the second `FROM` instruction - this produces a much smaller image by simply overlaying the newly-built binary on top of the regular `arm64v8/caddy` image.
 
 The [`xcaddy`](https://caddyserver.com/docs/build#xcaddy) tool is used to [build a new Caddy entrypoint](https://github.com/caddyserver/caddy/blob/4217217badf220d7d2c25f43f955fdc8454f2c64/cmd/caddy/main.go#L15..L25), with the provided modules. You can specify just a module name, or a name with a version (separated by `@`). You can also specify a specific version (can be a version tag or commit hash) of Caddy to build from. Read more about [`xcaddy` usage](https://github.com/caddyserver/xcaddy#command-usage).
 
@@ -208,7 +193,7 @@ If you prefer to use `docker compose` to run your stack, here's a sample service
 ```yaml
 services:
   caddy:
-    image: caddy:<version>
+    image: arm64v8/caddy:<version>
     restart: unless-stopped
     cap_add:
       - NET_ADMIN
@@ -231,13 +216,13 @@ Graceful reloads can then be conducted via `docker compose exec -w /etc/caddy ca
 
 # Image Variants
 
-The `caddy` images come in many flavors, each designed for a specific use case.
+The `arm64v8/caddy` images come in many flavors, each designed for a specific use case.
 
-## `caddy:<version>`
+## `arm64v8/caddy:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `caddy:<version>-alpine`
+## `arm64v8/caddy:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -245,14 +230,6 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `caddy:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
 # License
 
 View [license information](https://github.com/caddyserver/caddy/blob/master/LICENSE) for the software contained in this image.

cassandra/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `cassandra` official image](https://hub.docker.com/_/cassandra) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -68,7 +70,7 @@ Apache Cassandra is an open source distributed database management system design
 Starting a Cassandra instance is simple:
 
 ```console
-$ docker run --name some-cassandra --network some-network -d cassandra:tag
+$ docker run --name some-cassandra --network some-network -d arm64v8/cassandra:tag
 ```
 
 ... where `some-cassandra` is the name you want to assign to your container and `tag` is the tag specifying the Cassandra version you want. See the list above for relevant tags.
@@ -78,7 +80,7 @@ $ docker run --name some-cassandra --network some-network -d cassandra:tag
 Using the environment variables documented below, there are two cluster scenarios: instances on the same machine and instances on separate machines. For the same machine, start the instance as described above. To start other instances, just tell each new node where the first is.
 
 ```console
-$ docker run --name some-cassandra2 -d --network some-network -e CASSANDRA_SEEDS=some-cassandra cassandra:tag
+$ docker run --name some-cassandra2 -d --network some-network -e CASSANDRA_SEEDS=some-cassandra arm64v8/cassandra:tag
 ```
 
 For separate machines (ie, two VMs on a cloud provider), you need to tell Cassandra what IP address to advertise to the other nodes (since the address of the container is behind the docker bridge).
@@ -86,13 +88,13 @@ For separate machines (ie, two VMs on a cloud provider), you need to tell Cassan
 Assuming the first machine's IP address is `10.42.42.42` and the second's is `10.43.43.43`, start the first with exposed gossip port:
 
 ```console
-$ docker run --name some-cassandra -d -e CASSANDRA_BROADCAST_ADDRESS=10.42.42.42 -p 7000:7000 cassandra:tag
+$ docker run --name some-cassandra -d -e CASSANDRA_BROADCAST_ADDRESS=10.42.42.42 -p 7000:7000 arm64v8/cassandra:tag
 ```
 
 Then start a Cassandra container on the second machine, with the exposed gossip port and seed pointing to the first machine:
 
 ```console
-$ docker run --name some-cassandra -d -e CASSANDRA_BROADCAST_ADDRESS=10.43.43.43 -p 7000:7000 -e CASSANDRA_SEEDS=10.42.42.42 cassandra:tag
+$ docker run --name some-cassandra -d -e CASSANDRA_BROADCAST_ADDRESS=10.43.43.43 -p 7000:7000 -e CASSANDRA_SEEDS=10.42.42.42 arm64v8/cassandra:tag
 ```
 
 ## Connect to Cassandra from `cqlsh`
@@ -100,7 +102,7 @@ $ docker run --name some-cassandra -d -e CASSANDRA_BROADCAST_ADDRESS=10.43.43.43
 The following command starts another Cassandra container instance and runs `cqlsh` (Cassandra Query Language Shell) against your original Cassandra container, allowing you to execute CQL statements against your database instance:
 
 ```console
-$ docker run -it --network some-network --rm cassandra cqlsh some-cassandra
+$ docker run -it --network some-network --rm arm64v8/cassandra cqlsh some-cassandra
 ```
 
 More information about the CQL can be found in the [Cassandra documentation](https://cassandra.apache.org/doc/latest/cql/index.html).
@@ -123,7 +125,7 @@ $ docker logs some-cassandra
 
 The best way to provide configuration to the `cassandra` image is to provide a custom `/etc/cassandra/cassandra.yaml` file. There are many ways to provide this file to the container (via short `Dockerfile` with `FROM` + `COPY`, via [Docker Configs](https://docs.docker.com/engine/swarm/configs/), via runtime bind-mount, etc), the details of which are left as an exercise for the reader.
 
-To use a different file name (for example, to avoid all image-provided configuration behavior), use `-Dcassandra.config=/path/to/cassandra.yaml` as an argument to the image (as in, `docker run ... cassandra -Dcassandra.config=/path/to/cassandra.yaml`).
+To use a different file name (for example, to avoid all image-provided configuration behavior), use `-Dcassandra.config=/path/to/cassandra.yaml` as an argument to the image (as in, `docker run ... arm64v8/cassandra -Dcassandra.config=/path/to/cassandra.yaml`).
 
 There are a small number of environment variables supported by the image which will modify `/etc/cassandra/cassandra.yaml` in some way (but the script is modifying YAML, so is naturally fragile):
 
@@ -162,7 +164,7 @@ The Docker documentation is a good starting point for understanding the differen
 2.	Start your `cassandra` container like this:
 
 	```console
-	$ docker run --name some-cassandra -v /my/own/datadir:/var/lib/cassandra -d cassandra:tag
+	$ docker run --name some-cassandra -v /my/own/datadir:/var/lib/cassandra -d arm64v8/cassandra:tag
 	```
 
 The `-v /my/own/datadir:/var/lib/cassandra` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/cassandra` inside the container, where Cassandra by default will write its data files.

chronograf/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `chronograf` official image](https://hub.docker.com/_/chronograf) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -26,20 +28,12 @@ WARNING:
 
 -	[`1.7`, `1.7.17`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.7/Dockerfile)
 
--	[`1.7-alpine`, `1.7.17-alpine`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.7/alpine/Dockerfile)
-
 -	[`1.8`, `1.8.10`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.8/Dockerfile)
 
--	[`1.8-alpine`, `1.8.10-alpine`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.8/alpine/Dockerfile)
-
 -	[`1.9`, `1.9.4`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.9/Dockerfile)
 
--	[`1.9-alpine`, `1.9.4-alpine`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.9/alpine/Dockerfile)
-
 -	[`1.10`, `1.10.8`, `latest`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.10/Dockerfile)
 
--	[`1.10-alpine`, `1.10.8-alpine`, `alpine`](https://github.com/influxdata/influxdata-docker/blob/1bf4846c3b7df2b7fc4369af5989442ec3d5b899/chronograf/1.10/alpine/Dockerfile)
-
 # Quick reference (cont.)
 
 -	**Where to file issues**:  
@@ -72,7 +66,7 @@ Chronograf is InfluxData's open source web application. Use Chronograf with the
 Chronograf runs on port 8888. It can be run and accessed by exposing that port:
 
 ```console
-$ docker run -p 8888:8888 chronograf
+$ docker run -p 8888:8888 arm64v8/chronograf
 ```
 
 ### Mounting a volume
@@ -82,7 +76,7 @@ The Chronograf image exposes a shared volume under `/var/lib/chronograf`, so you
 ```console
 $ docker run -p 8888:8888 \
       -v $PWD:/var/lib/chronograf \
-      chronograf
+      arm64v8/chronograf
 ```
 
 Modify `$PWD` to the directory where you want to store data associated with the InfluxDB container.
@@ -92,7 +86,7 @@ You can also have Docker control the volume mountpoint by using a named volume.
 ```console
 $ docker run -p 8888:8888 \
       -v chronograf:/var/lib/chronograf \
-      chronograf
+      arm64v8/chronograf
 ```
 
 ### Using the container with InfluxDB
@@ -116,7 +110,7 @@ We can now start a Chronograf container that references this database.
 ```console
 $ docker run -p 8888:8888 \
       --net=influxdb \
-      chronograf --influxdb-url=http://influxdb:8086
+      arm64v8/chronograf --influxdb-url=http://influxdb:8086
 ```
 
 Try combining this with Telegraf to get dashboards for your infrastructure within minutes!
@@ -129,22 +123,6 @@ Starting in v1.10.5, Chronograf no longer run as the root user by default. If a
 
 See the [official docs](https://docs.influxdata.com/chronograf/latest/) for information on creating visualizations.
 
-# Image Variants
-
-The `chronograf` images come in many flavors, each designed for a specific use case.
-
-## `chronograf:<version>`
-
-This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
-
-## `chronograf:<version>-alpine`
-
-This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
-
-This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use [musl libc](https://musl.libc.org) instead of [glibc and friends](https://www.etalabs.net/compare_libcs.html), so software will often run into issues depending on the depth of their libc requirements/assumptions. See [this Hacker News comment thread](https://news.ycombinator.com/item?id=10782897) for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
-
-To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
-
 # License
 
 View [license information](https://github.com/influxdata/chronograf/blob/master/LICENSE) for the software contained in this image.

cirros/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `cirros` official image](https://hub.docker.com/_/cirros) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,7 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`0.6.3`, `0.6`, `0`, `latest`](https://github.com/tianon/docker-brew-cirros/blob/1821a0ca9eaf82280a2e953df56e88ab50178628/arches/amd64/Dockerfile)
+-	[`0.6.3`, `0.6`, `0`, `latest`](https://github.com/tianon/docker-brew-cirros/blob/1821a0ca9eaf82280a2e953df56e88ab50178628/arches/arm64v8/Dockerfile)
 
 # Quick reference (cont.)
 

clearlinux/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `clearlinux` official image](https://hub.docker.com/_/clearlinux) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # **DEPRECATION NOTICE**
 
 https://community.clearlinux.org/t/all-good-things-come-to-an-end-shutting-down-clear-linux-os/10716
@@ -30,7 +32,7 @@ https://community.clearlinux.org/t/all-good-things-come-to-an-end-shutting-down-
 
 # Supported tags and respective `Dockerfile` links
 
--	[`latest`, `base`](https://github.com/clearlinux/docker-brew-clearlinux/blob/03e2dcd390233733b398e72ce2382e54b5ef48a4/Dockerfile)
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -57,14 +59,14 @@ This serves as the official [Clear Linux OS](https://clearlinux.org) image.
 
 ![logo](https://raw.githubusercontent.com/docker-library/docs/dbe1941be63c87cc691b59d50f830f9dd7d69df9/clearlinux/logo.png)
 
-The `clearlinux:latest` tag will point to `clearlinux:base` which will track toward the latest release version of the distribution.
+The `arm64v8/clearlinux:latest` tag will point to `arm64v8/clearlinux:base` which will track toward the latest release version of the distribution.
 
 This image contains the os-core and os-core-update bundles, the latter can be used to add additional Clear Linux OS components (see [here](https://clearlinux.org/documentation/swupdate_about_sw_update.html) for more details about swupd and [here](https://clearlinux.org/documentation/bundles_overview.html) for more information on bundles).
 
 The following Dockerfile will install the editors and dev-utils bundles on top of the base image
 
 ```sh
-FROM clearlinux:base
+FROM arm64v8/clearlinux:base
 RUN swupd bundle-add editors dev-utils
 ```
 

clefos/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `clefos` official image](https://hub.docker.com/_/clefos) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # **DEPRECATION NOTICE**
 
 With [the EOL of CentOS 7 (June 30, 2024)](https://www.redhat.com/en/topics/linux/centos-linux-eol), this image/project is [officially deprecated](https://github.com/docker-library/official-images/pull/7964#issuecomment-2253636315). Please adjust your usage accordingly.
@@ -28,7 +30,7 @@ With [the EOL of CentOS 7 (June 30, 2024)](https://www.redhat.com/en/topics/linu
 
 # Supported tags and respective `Dockerfile` links
 
-**No supported tags**
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -57,7 +59,7 @@ ClefOS Linux is a community-supported distribution for IBM Z (aka "mainframe") d
 
 ## ClefOS image documentation
 
-The `clefos:latest` tag is always the most recent version currently available.
+The `arm64v8/clefos:latest` tag is always the most recent version currently available.
 
 ### Building the Base Image
 
@@ -69,7 +71,7 @@ The `VERSION` file contains the id of the current ClefOS version and will be add
 
 ### Rolling builds
 
-The ClefOS Project offers regularly updated images for all active releases. These images will be updated monthly or as needed for emergency fixes. These rolling updates are tagged with the major version number and minor tags as well. For example, if 7.4.1708 is the most current then the build will result in `clefos:7` and `clefos:7.4.1708`. When the next minor level is available then `clefos:7` and `clefos:7.x.yymm` will be identical.
+The ClefOS Project offers regularly updated images for all active releases. These images will be updated monthly or as needed for emergency fixes. These rolling updates are tagged with the major version number and minor tags as well. For example, if 7.4.1708 is the most current then the build will result in `arm64v8/clefos:7` and `arm64v8/clefos:7.4.1708`. When the next minor level is available then `arm64v8/clefos:7` and `arm64v8/clefos:7.x.yymm` will be identical.
 
 ### Overlayfs and yum
 
@@ -81,12 +83,12 @@ By default, the ClefOS containers are built using yum's `nodocs` option, which h
 
 ## Systemd integration
 
-Systemd is not included in both the `clefos:7` and `clefos:latest` base containers, but can be created from these bases:
+Systemd is not included in both the `arm64v8/clefos:7` and `arm64v8/clefos:latest` base containers, but can be created from these bases:
 
 ### Dockerfile for systemd base image
 
 ```dockerfile
-FROM 		clefos:7
+FROM 		arm64v8/clefos:7
 
 ENV 		container docker
 

clickhouse/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `clickhouse` official image](https://hub.docker.com/_/clickhouse) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -80,7 +82,7 @@ For more information and documentation see https://clickhouse.com/.
 ### start server instance
 
 ```bash
-docker run -d --name some-clickhouse-server --ulimit nofile=262144:262144 clickhouse
+docker run -d --name some-clickhouse-server --ulimit nofile=262144:262144 arm64v8/clickhouse
 ```
 
 By default, ClickHouse will be accessible only via the Docker network. See the **networking** section below.
@@ -90,7 +92,7 @@ By default, starting above server instance will be run as the `default` user wit
 ### connect to it from a native client
 
 ```bash
-docker run -it --rm --network=container:some-clickhouse-server --entrypoint clickhouse-client clickhouse
+docker run -it --rm --network=container:some-clickhouse-server --entrypoint clickhouse-client arm64v8/clickhouse
 # OR
 docker exec -it some-clickhouse-server clickhouse-client
 ```
@@ -119,7 +121,7 @@ docker rm some-clickhouse-server
 You can expose your ClickHouse running in docker by [mapping a particular port](https://docs.docker.com/config/containers/container-networking/) from inside the container using host ports:
 
 ```bash
-docker run -d -p 18123:8123 -p19000:9000 -e CLICKHOUSE_PASSWORD=changeme --name some-clickhouse-server --ulimit nofile=262144:262144 clickhouse
+docker run -d -p 18123:8123 -p19000:9000 -e CLICKHOUSE_PASSWORD=changeme --name some-clickhouse-server --ulimit nofile=262144:262144 arm64v8/clickhouse
 echo 'SELECT version()' | curl 'http://localhost:18123/?password=changeme' --data-binary @-
 ```
 
@@ -128,7 +130,7 @@ echo 'SELECT version()' | curl 'http://localhost:18123/?password=changeme' --dat
 Or by allowing the container to use [host ports directly](https://docs.docker.com/network/host/) using `--network=host` (also allows achieving better network performance):
 
 ```bash
-docker run -d --network=host --name some-clickhouse-server --ulimit nofile=262144:262144 clickhouse
+docker run -d --network=host --name some-clickhouse-server --ulimit nofile=262144:262144 arm64v8/clickhouse
 echo 'SELECT version()' | curl 'http://localhost:8123/' --data-binary @-
 ```
 
@@ -147,7 +149,7 @@ Typically you may want to mount the following folders inside your container to a
 docker run -d \
     -v "$PWD/ch_data:/var/lib/clickhouse/" \
     -v "$PWD/ch_logs:/var/log/clickhouse-server/" \
-    --name some-clickhouse-server --ulimit nofile=262144:262144 clickhouse
+    --name some-clickhouse-server --ulimit nofile=262144:262144 arm64v8/clickhouse
 ```
 
 You may also want to mount:
@@ -165,7 +167,7 @@ They are optional and can be enabled using the following [docker command-line ar
 ```bash
 docker run -d \
     --cap-add=SYS_NICE --cap-add=NET_ADMIN --cap-add=IPC_LOCK \
-    --name some-clickhouse-server --ulimit nofile=262144:262144 clickhouse
+    --name some-clickhouse-server --ulimit nofile=262144:262144 arm64v8/clickhouse
 ```
 
 Read more in [knowledge base](https://clickhouse.com/docs/knowledgebase/configure_cap_ipc_lock_and_cap_sys_nice_in_docker).
@@ -179,14 +181,14 @@ ClickHouse configuration is represented with a file "config.xml" ([documentation
 ### Start server instance with custom configuration
 
 ```bash
-docker run -d --name some-clickhouse-server --ulimit nofile=262144:262144 -v /path/to/your/config.xml:/etc/clickhouse-server/config.xml clickhouse
+docker run -d --name some-clickhouse-server --ulimit nofile=262144:262144 -v /path/to/your/config.xml:/etc/clickhouse-server/config.xml arm64v8/clickhouse
 ```
 
 ### Start server as custom user
 
 ```bash
 # $PWD/data/clickhouse should exist and be owned by current user
-docker run --rm --user "${UID}:${GID}" --name some-clickhouse-server --ulimit nofile=262144:262144 -v "$PWD/logs/clickhouse:/var/log/clickhouse-server" -v "$PWD/data/clickhouse:/var/lib/clickhouse" clickhouse
+docker run --rm --user "${UID}:${GID}" --name some-clickhouse-server --ulimit nofile=262144:262144 -v "$PWD/logs/clickhouse:/var/log/clickhouse-server" -v "$PWD/data/clickhouse:/var/lib/clickhouse" arm64v8/clickhouse
 ```
 
 When you use the image with local directories mounted, you probably want to specify the user to maintain the proper file ownership. Use the `--user` argument and mount `/var/lib/clickhouse` and `/var/log/clickhouse-server` inside the container. Otherwise, the image will complain and not start.
@@ -194,7 +196,7 @@ When you use the image with local directories mounted, you probably want to spec
 ### Start server from root (useful in case of enabled user namespace)
 
 ```bash
-docker run --rm -e CLICKHOUSE_RUN_AS_ROOT=1 --name clickhouse-server-userns -v "$PWD/logs/clickhouse:/var/log/clickhouse-server" -v "$PWD/data/clickhouse:/var/lib/clickhouse" clickhouse
+docker run --rm -e CLICKHOUSE_RUN_AS_ROOT=1 --name clickhouse-server-userns -v "$PWD/logs/clickhouse:/var/log/clickhouse-server" -v "$PWD/data/clickhouse:/var/lib/clickhouse" arm64v8/clickhouse
 ```
 
 ### How to create default database and user on starting
@@ -202,7 +204,7 @@ docker run --rm -e CLICKHOUSE_RUN_AS_ROOT=1 --name clickhouse-server-userns -v "
 Sometimes you may want to create a user (user named `default` is used by default) and database on a container start. You can do it using environment variables `CLICKHOUSE_DB`, `CLICKHOUSE_USER`, `CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT` and `CLICKHOUSE_PASSWORD`:
 
 ```bash
-docker run --rm -e CLICKHOUSE_DB=my_database -e CLICKHOUSE_USER=username -e CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT=1 -e CLICKHOUSE_PASSWORD=password -p 9000:9000/tcp clickhouse
+docker run --rm -e CLICKHOUSE_DB=my_database -e CLICKHOUSE_USER=username -e CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT=1 -e CLICKHOUSE_PASSWORD=password -p 9000:9000/tcp arm64v8/clickhouse
 ```
 
 #### Managing `default` user
@@ -212,7 +214,7 @@ The user `default` has disabled network access by default in the case none of `C
 There's a way to make `default` user insecurely available by setting environment variable `CLICKHOUSE_SKIP_USER_SETUP` to 1:
 
 ```bash
-docker run --rm -e CLICKHOUSE_SKIP_USER_SETUP=1 -p 9000:9000/tcp clickhouse
+docker run --rm -e CLICKHOUSE_SKIP_USER_SETUP=1 -p 9000:9000/tcp arm64v8/clickhouse
 ```
 
 ## How to extend this image

clojure/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `clojure` official image](https://hub.docker.com/_/clojure) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -26,8 +28,6 @@ WARNING:
 
 -	[`latest`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-25/latest/Dockerfile)
 
--	[`temurin-8-lein-2.12.0-alpine`, `temurin-8-lein-alpine`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/eclipse-temurin-8-jdk-alpine/lein/Dockerfile)
-
 -	[`temurin-8-lein-2.12.0-bookworm`, `temurin-8-lein-bookworm`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-8/lein/Dockerfile)
 
 -	[`temurin-8-lein-2.12.0-bookworm-slim`, `temurin-8-lein-bookworm-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-slim-8/lein/Dockerfile)
@@ -44,8 +44,6 @@ WARNING:
 
 -	[`temurin-8-lein-2.12.0-trixie-slim`, `temurin-8-lein-trixie-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-trixie-slim-8/lein/Dockerfile)
 
--	[`temurin-8-alpine`, `temurin-8-tools-deps-1.12.3.1577-alpine`, `temurin-8-tools-deps-alpine`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/eclipse-temurin-8-jdk-alpine/tools-deps/Dockerfile)
-
 -	[`temurin-8-bookworm`, `temurin-8-tools-deps-1.12.3.1577-bookworm`, `temurin-8-tools-deps-bookworm`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-8/tools-deps/Dockerfile)
 
 -	[`temurin-8-bookworm-slim`, `temurin-8-tools-deps-1.12.3.1577-bookworm-slim`, `temurin-8-tools-deps-bookworm-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-slim-8/tools-deps/Dockerfile)
@@ -62,8 +60,6 @@ WARNING:
 
 -	[`temurin-8-tools-deps-1.12.3.1577-trixie-slim`, `temurin-8-tools-deps-trixie-slim`, `temurin-8-trixie-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-trixie-slim-8/tools-deps/Dockerfile)
 
--	[`temurin-11-lein-2.12.0-alpine`, `temurin-11-lein-alpine`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/eclipse-temurin-11-jdk-alpine/lein/Dockerfile)
-
 -	[`temurin-11-lein-2.12.0-bookworm`, `temurin-11-lein-bookworm`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-11/lein/Dockerfile)
 
 -	[`temurin-11-lein-2.12.0-bookworm-slim`, `temurin-11-lein-bookworm-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-slim-11/lein/Dockerfile)
@@ -80,8 +76,6 @@ WARNING:
 
 -	[`temurin-11-lein-2.12.0-trixie-slim`, `temurin-11-lein-trixie-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-trixie-slim-11/lein/Dockerfile)
 
--	[`temurin-11-alpine`, `temurin-11-tools-deps-1.12.3.1577-alpine`, `temurin-11-tools-deps-alpine`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/eclipse-temurin-11-jdk-alpine/tools-deps/Dockerfile)
-
 -	[`temurin-11-bookworm`, `temurin-11-tools-deps-1.12.3.1577-bookworm`, `temurin-11-tools-deps-bookworm`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-11/tools-deps/Dockerfile)
 
 -	[`temurin-11-bookworm-slim`, `temurin-11-tools-deps-1.12.3.1577-bookworm-slim`, `temurin-11-tools-deps-bookworm-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-slim-11/tools-deps/Dockerfile)
@@ -98,8 +92,6 @@ WARNING:
 
 -	[`temurin-11-tools-deps-1.12.3.1577-trixie-slim`, `temurin-11-tools-deps-trixie-slim`, `temurin-11-trixie-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-trixie-slim-11/tools-deps/Dockerfile)
 
--	[`temurin-17-lein-2.12.0-alpine`, `temurin-17-lein-alpine`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/eclipse-temurin-17-jdk-alpine/lein/Dockerfile)
-
 -	[`temurin-17-lein-2.12.0-bookworm`, `temurin-17-lein-bookworm`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-17/lein/Dockerfile)
 
 -	[`temurin-17-lein-2.12.0-bookworm-slim`, `temurin-17-lein-bookworm-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-slim-17/lein/Dockerfile)
@@ -116,8 +108,6 @@ WARNING:
 
 -	[`temurin-17-lein-2.12.0-trixie-slim`, `temurin-17-lein-trixie-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-trixie-slim-17/lein/Dockerfile)
 
--	[`temurin-17-alpine`, `temurin-17-tools-deps-1.12.3.1577-alpine`, `temurin-17-tools-deps-alpine`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/eclipse-temurin-17-jdk-alpine/tools-deps/Dockerfile)
-
 -	[`temurin-17-bookworm`, `temurin-17-tools-deps-1.12.3.1577-bookworm`, `temurin-17-tools-deps-bookworm`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-17/tools-deps/Dockerfile)
 
 -	[`temurin-17-bookworm-slim`, `temurin-17-tools-deps-1.12.3.1577-bookworm-slim`, `temurin-17-tools-deps-bookworm-slim`](https://github.com/Quantisan/docker-clojure/blob/6938e39125e2607ccc427065e6dfd11adf6e7527/target/debian-bookworm-slim-17/tools-deps/Dockerfile)
@@ -255,7 +245,7 @@ But you can also append a hyphen and the version of that tool you'd like to use.
 Add a `Dockerfile` to an existing Leiningen/Clojure project with the following contents:
 
 ```dockerfile
-FROM clojure
+FROM arm64v8/clojure
 COPY . /usr/src/app
 WORKDIR /usr/src/app
 CMD ["lein", "run"]
@@ -271,7 +261,7 @@ $ docker run -it --rm --name my-running-app my-clojure-app
 While the above is the most straightforward example of a `Dockerfile`, it does have some drawbacks. The `lein run` command will download your dependencies, compile the project, and then run it. That's a lot of work, all of which you may not want done every time you run the image. To get around this, you can download the dependencies and compile the project ahead of time. This will significantly reduce startup time when you run your image.
 
 ```dockerfile
-FROM clojure
+FROM arm64v8/clojure
 RUN mkdir -p /usr/src/app
 WORKDIR /usr/src/app
 COPY project.clj /usr/src/app/
@@ -290,7 +280,7 @@ You can then build and run the image as above.
 If you have an existing Lein/Clojure project, it's fairly straightforward to compile your project into a jar from a container:
 
 ```console
-$ docker run -it --rm -v "$PWD":/usr/src/app -w /usr/src/app clojure lein uberjar
+$ docker run -it --rm -v "$PWD":/usr/src/app -w /usr/src/app arm64v8/clojure lein uberjar
 ```
 
 This will build your project into a jar file located in your project's `target/uberjar` directory.
@@ -301,9 +291,9 @@ See [the official image README](https://github.com/Quantisan/docker-clojure/blob
 
 # Image Variants
 
-The `clojure` images come in many flavors, each designed for a specific use case.
+The `arm64v8/clojure` images come in many flavors, each designed for a specific use case.
 
-## `clojure:<version>`
+## `arm64v8/clojure:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
@@ -311,7 +301,11 @@ Some of these tags may have names like bookworm, bullseye, or trixie in them. Th
 
 Some of these tags may have names like jammy or noble in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
 
-## `clojure:<version>-alpine`
+## `arm64v8/clojure:<version>-slim`
+
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/clojure`. Unless you are working in an environment where *only* the `arm64v8/clojure` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+
+## `arm64v8/clojure:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -319,10 +313,6 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `clojure:<version>-slim`
-
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `clojure`. Unless you are working in an environment where *only* the `clojure` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
-
 # License
 
 View [license information](http://clojure.org/license) for the software contained in this image.

composer/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `composer` official image](https://hub.docker.com/_/composer) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -64,7 +66,7 @@ You can read more about Composer in our [official documentation](https://getcomp
 ```console
 $ docker run --rm --interactive --tty \
   --volume $PWD:/app \
-  composer <command>
+  arm64v8/composer <command>
 ```
 
 ### Persist cache / global configuration
@@ -75,7 +77,7 @@ You can bind mount the Composer home directory from your host to the container t
 $ docker run --rm --interactive --tty \
   --volume $PWD:/app \
   --volume ${COMPOSER_HOME:-$HOME/.composer}:/tmp \
-  composer <command>
+  arm64v8/composer <command>
 ```
 
 **Note:** this relies on the fact that the `COMPOSER_HOME` value is set to `/tmp` in the image by default.
@@ -89,7 +91,7 @@ $ docker run --rm --interactive --tty \
   --volume ${COMPOSER_HOME:-$HOME/.config/composer}:$COMPOSER_HOME \
   --volume ${COMPOSER_CACHE_DIR:-$HOME/.cache/composer}:$COMPOSER_CACHE_DIR \
   --volume $PWD:/app \
-  composer <command>
+  arm64v8/composer <command>
 ```
 
 ### Filesystem permissions
@@ -100,7 +102,7 @@ By default, Composer runs as root inside the container. This can lead to permiss
 $ docker run --rm --interactive --tty \
   --volume $PWD:/app \
   --user $(id -u):$(id -g) \
-  composer <command>
+  arm64v8/composer <command>
 ```
 
 See: https://docs.docker.com/engine/reference/run/#user for details.
@@ -117,7 +119,7 @@ $ eval $(ssh-agent); \
   --volume $PWD:/app \
   --volume $SSH_AUTH_SOCK:/ssh-auth.sock \
   --env SSH_AUTH_SOCK=/ssh-auth.sock \
-  composer <command>
+  arm64v8/composer <command>
 ```
 
 **Note:** On OSX this requires Docker For Mac v2.2.0.0 or later, see [docker/for-mac#410](https://github.com/docker/for-mac/issues/410).
@@ -133,7 +135,7 @@ $ eval $(ssh-agent); \
   --volume /etc/group:/etc/group:ro \
   --env SSH_AUTH_SOCK=/ssh-auth.sock \
   --user $(id -u):$(id -g) \
-  composer <command>
+  arm64v8/composer <command>
 ```
 
 # Troubleshooting
@@ -151,7 +153,7 @@ Suggestions:
 	**Note:** Docker 17.05 introduced [multi-stage builds](https://docs.docker.com/develop/develop-images/multistage-build/), simplifying this enormously:
 
 	```dockerfile
-	COPY --from=composer /usr/bin/composer /usr/bin/composer
+	COPY --from=arm64v8/composer /usr/bin/composer /usr/bin/composer
 	```
 
 -	(alternatively) specify the target [platform](https://getcomposer.org/doc/06-config.md#platform) / extension(s) in your `composer.json`:
@@ -172,7 +174,7 @@ Suggestions:
 	```console
 	$ docker run --rm --interactive --tty \
 	  --volume $PWD:/app \
-	  composer install --ignore-platform-reqs --no-scripts
+	  arm64v8/composer install --ignore-platform-reqs --no-scripts
 	```
 
 # License

convertigo/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `convertigo` official image](https://hub.docker.com/_/convertigo) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -64,7 +66,7 @@ Convertigo Community edition brought to you by Convertigo SA (Paris & San Franci
 ## Quick start
 
 ```console
-$ docker run --name C8O -d -p 28080:28080 convertigo
+$ docker run --name C8O -d -p 28080:28080 arm64v8/convertigo
 ```
 
 This will start a container running the minimum Convertigo server. Convertigo uses images' **/workspace** directory to store configuration file and deployed projects as an Docker volume.
@@ -86,7 +88,7 @@ $ docker run -d --name fullsync couchdb:3.2.2
 Then launch Convertigo and link it to the running 'fullsync' container. Convertigo Low Code sever will automatically use it as its fullsync repository.
 
 ```console
-$ docker run -d --name C8O --link fullsync:couchdb -p 28080:28080 convertigo
+$ docker run -d --name C8O --link fullsync:couchdb -p 28080:28080 arm64v8/convertigo
 ```
 
 ## Use embedded PouchDB as FullSync engine (not for production)
@@ -96,7 +98,7 @@ Convertigo FullSync is designed to use CouchDB server or cluster. Convertigo Ful
 It can be enabled directly at startup:
 
 ```console
-$ docker run -d --name C8O -e JAVA_OPTS="-Dconvertigo.engine.fullsync.pouchdb=true" -p 28080:28080 convertigo
+$ docker run -d --name C8O -e JAVA_OPTS="-Dconvertigo.engine.fullsync.pouchdb=true" -p 28080:28080 arm64v8/convertigo
 ```
 
 ## Link Convertigo Low Code Server to a Billing & Analytics database
@@ -111,7 +113,7 @@ $ docker run -d --name C8O --link [mysql-container]:mysql -p 28080:28080
             -Dconvertigo.engine.billing.persistence.jdbc.username=[username for the c8oAnalytics db] \
             -Dconvertigo.engine.billing.persistence.jdbc.password=[password for specified db user]   \
             -Dconvertigo.engine.billing.persistence.jdbc.url=jdbc:mysql://mysql:3306/c8oAnalytics"   \
-convertigo
+arm64v8/convertigo
 ```
 
 ## Where is Convertigo Low Code server storing deployed projects
@@ -119,7 +121,7 @@ convertigo
 Projects are deployed in the Convertigo workspace, a simple file system directory. You can map the docker container **/workspace** to your physical system by using:
 
 ```console
-$ docker run --name C8O -v $(pwd):/workspace -d -p 28080:28080 convertigo
+$ docker run --name C8O -v $(pwd):/workspace -d -p 28080:28080 arm64v8/convertigo
 ```
 
 You can share the same workspace by all Convertigo containers. In this case, when you deploy a project on a Convertigo container, it will be seen by others. This is the best way to build multi-instance load balanced Convertigo server farms.
@@ -138,7 +140,7 @@ To avoid log and cache mixing, you have to add 2 variables for instance specific
 If you want to make a vertical image ready to start with your application inside, you have to have your built projects **.car** files next to your `Dockerfile`:
 
 ```console
-FROM convertigo
+FROM arm64v8/convertigo
 COPY myProject.car /usr/local/tomcat/webapps/convertigo/WEB-INF/default_user_workspace/projects/
 COPY myDependency.car /usr/local/tomcat/webapps/convertigo/WEB-INF/default_user_workspace/projects/
 ```
@@ -160,7 +162,7 @@ These accounts can be configured through the **administration console** and save
 You can change the default administration account :
 
 ```console
-$ docker run -d --name C8O -e CONVERTIGO_ADMIN_USER=administrator -e CONVERTIGO_ADMIN_PASSWORD=s3cret -p 28080:28080 convertigo
+$ docker run -d --name C8O -e CONVERTIGO_ADMIN_USER=administrator -e CONVERTIGO_ADMIN_PASSWORD=s3cret -p 28080:28080 arm64v8/convertigo
 ```
 
 ### `CONVERTIGO_TESTPLATFORM_USER` and `CONVERTIGO_TESTPLATFORM_PASSWORD` Environment variables
@@ -168,7 +170,7 @@ $ docker run -d --name C8O -e CONVERTIGO_ADMIN_USER=administrator -e CONVERTIGO_
 You can lock the **testplatform** by setting the account :
 
 ```console
-$ docker run -d --name C8O -e CONVERTIGO_TESTPLATFORM_USER=tp_user -e CONVERTIGO_TESTPLATFORM_PASSWORD=s3cret -p 28080:28080 convertigo
+$ docker run -d --name C8O -e CONVERTIGO_TESTPLATFORM_USER=tp_user -e CONVERTIGO_TESTPLATFORM_PASSWORD=s3cret -p 28080:28080 arm64v8/convertigo
 ```
 
 ## HTTPS / SSL Configuration
@@ -186,13 +188,13 @@ If you have an existing certificate and a private key, you can put them in **PEM
 -	`chain.pem` : the optional chain of certificates not included in `cert.pem` using the PEM format
 
 ```console
-$ docker run -d --name C8O -v <my SSL folder>:/ssl -p 28443:28443 convertigo
+$ docker run -d --name C8O -v <my SSL folder>:/ssl -p 28443:28443 arm64v8/convertigo
 ```
 
 If you want to expose both **HTTP** and **HTTPS** you can expose both **ports**:
 
 ```console
-$ docker run -d --name C8O -v <my SSL folder>:/ssl -p 28080:28080 -p 28443:28443 convertigo
+$ docker run -d --name C8O -v <my SSL folder>:/ssl -p 28080:28080 -p 28443:28443 arm64v8/convertigo
 ```
 
 ### Provide existing certificate using environment variables
@@ -207,7 +209,7 @@ If you cannot mount a volume, you can probably add environment variables of prev
 $ SSL_KEY_B64=$(base64 key.pem)
 $ SSL_CERT_B64=$(base64 cert.pem)
 $ SSL_CHAIN_B64=$(base64 chain.pem)
-$ docker run -d --name C8O -e SSL_KEY_B64="$SSL_KEY_B64" -e SSL_CERT_B64="$SSL_CERT_B64" -e SSL_CHAIN_B64="$SSL_CHAIN_B64" -p 28443:28443 convertigo
+$ docker run -d --name C8O -e SSL_KEY_B64="$SSL_KEY_B64" -e SSL_CERT_B64="$SSL_CERT_B64" -e SSL_CHAIN_B64="$SSL_CHAIN_B64" -p 28443:28443 arm64v8/convertigo
 ```
 
 ### Generate and use a self-signed certificate
@@ -217,13 +219,13 @@ If you don't have certificate file, you can dynamically generate one for the fir
 Use the `SSL_SELFSIGNED` environment variable to indicate for what domain you want generate certificate.
 
 ```console
-$ docker run -d --name C8O -e SSL_SELFSIGNED=mycomputer -p 28443:28443 convertigo
+$ docker run -d --name C8O -e SSL_SELFSIGNED=mycomputer -p 28443:28443 arm64v8/convertigo
 ```
 
 Generated files can be retrieved if the `/ssl` mount point is configured on folder without `cert.pem` nor `key.pem`.
 
 ```console
-$ docker run -d --name C8O -v <my empty SSL folder>:/ssl -e SSL_SELFSIGNED=mycomputer -p 28443:28443 convertigo
+$ docker run -d --name C8O -v <my empty SSL folder>:/ssl -e SSL_SELFSIGNED=mycomputer -p 28443:28443 arm64v8/convertigo
 ```
 
 ## `JAVA_OPTS` Environment variable
@@ -233,7 +235,7 @@ Convertigo is based on a **Java** process with some defaults **JVM** options. Yo
 Add any **Java JVM** options such as -D[something] :
 
 ```console
-$ docker run -d --name C8O -e JAVA_OPTS="-DjvmRoute=server1" -p 28080:28080 convertigo
+$ docker run -d --name C8O -e JAVA_OPTS="-DjvmRoute=server1" -p 28080:28080 arm64v8/convertigo
 ```
 
 [Here the list of convertigo specific properties](https://www.convertigo.com/documentation/latest/operating-guide/appendixes/#list-of-convertigo-java-system-properties) (don't forget the `-Dconvertigo.engine.` prefix).
@@ -255,7 +257,7 @@ Convertigo tries to allocate this amount of memory in the container and will aut
 The default `JXMX` value is `2048` and can be defined :
 
 ```console
-$ docker run -d --name C8O -e JXMX="4096" -p 28080:28080 convertigo
+$ docker run -d --name C8O -e JXMX="4096" -p 28080:28080 arm64v8/convertigo
 ```
 
 ## `COOKIE_PATH` Environment variable
@@ -265,7 +267,7 @@ Convertigo generates a `JSESSIONID` to maintain the user session and stores in a
 The default `COOKIE_PATH` value is `/` and can be defined :
 
 ```console
-$ docker run -d --name C8O -e COOKIE_PATH="/convertigo" -p 28080:28080 convertigo
+$ docker run -d --name C8O -e COOKIE_PATH="/convertigo" -p 28080:28080 arm64v8/convertigo
 ```
 
 ## `COOKIE_SECURE` Environment variable
@@ -277,7 +279,7 @@ The Secure flag can be enabled by setting the `COOKIE_SECURE` environment variab
 The default `COOKIE_SECURE` value is `false` and can be defined :
 
 ```console
-$ docker run -d --name C8O -e COOKIE_SECURE="true" -p 28080:28080 convertigo
+$ docker run -d --name C8O -e COOKIE_SECURE="true" -p 28080:28080 arm64v8/convertigo
 ```
 
 **Note :** if you have set the **SSL** configuration and you access the **HTTPS 28443** port, cookies are automatically `Secure`.
@@ -289,7 +291,7 @@ Allow to configure the **SameSite** parameter for generated cookies. Can be empt
 The default `COOKIE_SAMESITE` value is **empty** and can be defined this way:
 
 ```console
-$ docker run -d --name C8O -e COOKIE_SAMESITE=lax -p 28080:28080 convertigo
+$ docker run -d --name C8O -e COOKIE_SAMESITE=lax -p 28080:28080 arm64v8/convertigo
 ```
 
 ## `SESSION_TIMEOUT` Environment variable
@@ -299,7 +301,7 @@ Allow to configure the default Tomcat **session-timeout** in minutes. This value
 The default `SESSION_TIMEOUT` value is **30** and can be defined this way:
 
 ```console
-$ docker run -d --name C8O -e SESSION_TIMEOUT=5 -p 28080:28080 convertigo
+$ docker run -d --name C8O -e SESSION_TIMEOUT=5 -p 28080:28080 arm64v8/convertigo
 ```
 
 ## `DISABLE_SUDO` Environment variable
@@ -309,7 +311,7 @@ The image includes **sudo** command line, configured to allow the **convertigo**
 The default `DISABLE_SUDO` value is **empty** and can be defined this way:
 
 ```console
-$ docker run -d --name C8O -e DISABLE_SUDO=true -p 28080:28080 convertigo
+$ docker run -d --name C8O -e DISABLE_SUDO=true -p 28080:28080 arm64v8/convertigo
 ```
 
 ## `ENABLE_JDWP_DEBUG` Environment variable
@@ -319,7 +321,7 @@ Convertigo operates using the JVM (Java Virtual Machine). To enable remote debug
 The default `ENABLE_JDWP_DEBUG` value is **false** and can be defined this way:
 
 ```console
-$ docker run -d –name C8O -e ENABLE_JDWP_DEBUG=true -p 28080:28080 convertigo
+$ docker run -d –name C8O -e ENABLE_JDWP_DEBUG=true -p 28080:28080 arm64v8/convertigo
 ```
 
 ## Pre-configurated Docker Compose file

couchbase/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `couchbase` official image](https://hub.docker.com/_/couchbase) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

couchdb/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `couchdb` official image](https://hub.docker.com/_/couchdb) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -68,7 +70,7 @@ Store your data safely, on your own servers, or with any leading cloud provider.
 Starting a CouchDB instance is simple:
 
 ```console
-$ docker run -d --name my-couchdb couchdb:tag
+$ docker run -d --name my-couchdb arm64v8/couchdb:tag
 ```
 
 where `my-couchdb` is the name you want to assign to your container, and `tag` is the tag specifying the CouchDB version you want. See the list above for relevant tags.
@@ -86,7 +88,7 @@ $ docker run --name my-couchdb-app --link my-couchdb:couchdb -d app-that-uses-co
 If you want to expose the port to the outside world, run
 
 ```console
-$ docker run -p 5984:5984 -d couchdb
+$ docker run -p 5984:5984 -d arm64v8/couchdb
 ```
 
 *WARNING*: Do not do this until you have established an admin user and setup permissions correctly on any databases you have created.
@@ -151,7 +153,7 @@ The Docker documentation is a good starting point for understanding the differen
 2.	Start your `couchdb` container like this:
 
 ```bash
-$ docker run --name some-%%REPO% -v /home/couchdb/data:/opt/couchdb/data -d couchdb:tag
+$ docker run --name some-%%REPO% -v /home/couchdb/data:/opt/couchdb/data -d arm64v8/couchdb:tag
 ```
 
 The `-v /home/couchdb/data:/opt/couchdb/data` part of the command mounts the `/home/couchdb/data` directory from the underlying host system as `/opt/couchdb/data` inside the container, where CouchDB by default will write its data files.
@@ -171,7 +173,7 @@ The node will also start in [admin party mode](https://docs.couchdb.org/en/stabl
 You can also use the two environment variables `COUCHDB_USER` and `COUCHDB_PASSWORD` to set up an admin user:
 
 ```console
-$ docker run -e COUCHDB_USER=admin -e COUCHDB_PASSWORD=password -d couchdb
+$ docker run -e COUCHDB_USER=admin -e COUCHDB_PASSWORD=password -d arm64v8/couchdb
 ```
 
 Note that if you are setting up a clustered CouchDB, you will want to pre-hash this password and use the identical hashed text across all nodes to ensure sessions work correctly when a load balancer is placed in front of the cluster. Hashing can be accomplished by running the container with the `/opt/couchdb/etc/local.d` directory mounted as a volume, allowing CouchDB to hash the password you set, then copying out the hashed version and using this value in the future.
@@ -183,7 +185,7 @@ The CouchDB configuration is specified in `.ini` files in `/opt/couchdb/etc`. Ta
 If you want to use a customized CouchDB configuration, you can create your configuration file in a directory on the host machine and then mount that directory as `/opt/couchdb/etc/local.d` inside the `couchdb` container.
 
 ```console
-$ docker run --name my-couchdb -v /home/couchdb/etc:/opt/couchdb/etc/local.d -d couchdb
+$ docker run --name my-couchdb -v /home/couchdb/etc:/opt/couchdb/etc/local.d -d arm64v8/couchdb
 ```
 
 The `-v /home/couchdb/etc:/opt/couchdb/etc/local.d` part of the command mounts the `/home/couchdb/etc` directory from the underlying host system as `/opt/couchdb/etc/local.d` inside the container, where CouchDB by default will write its dynamic configuration files.
@@ -193,7 +195,7 @@ You can also use `couchdb` as the base image for your own couchdb instance and p
 Example Dockerfile:
 
 ```dockerfile
-FROM couchdb
+FROM arm64v8/couchdb
 
 COPY local.ini /opt/couchdb/etc/
 ```

crate/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `crate` official image](https://hub.docker.com/_/crate) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -77,7 +79,7 @@ CrateDB provides an [Admin UI](https://crate.io/docs/crate/admin-ui/):
 Spin up this Docker image like so:
 
 ```console
-$ docker run --publish 4200:4200 --publish 5432:5432 crate -Cdiscovery.type=single-node
+$ docker run --publish 4200:4200 --publish 5432:5432 arm64v8/crate -Cdiscovery.type=single-node
 ```
 
 Visit the [getting started](https://crate.io/docs/crate/tutorials/en/latest/install-run/) page to see all the available download and install options.

dart/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `dart` official image](https://hub.docker.com/_/dart) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

debian/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `debian` official image](https://hub.docker.com/_/debian) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,61 +26,61 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`bookworm`, `bookworm-20251020`, `12.12`, `12`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/bookworm/oci/index.json)
+-	[`bookworm`, `bookworm-20251020`, `12.12`, `12`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/bookworm/oci/index.json)
 
--	[`bookworm-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/bookworm/backports/Dockerfile)
+-	[`bookworm-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/bookworm/backports/Dockerfile)
 
--	[`bookworm-slim`, `bookworm-20251020-slim`, `12.12-slim`, `12-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/bookworm/slim/oci/index.json)
+-	[`bookworm-slim`, `bookworm-20251020-slim`, `12.12-slim`, `12-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/bookworm/slim/oci/index.json)
 
--	[`bullseye`, `bullseye-20251020`, `11.11`, `11`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/bullseye/oci/index.json)
+-	[`bullseye`, `bullseye-20251020`, `11.11`, `11`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/bullseye/oci/index.json)
 
--	[`bullseye-slim`, `bullseye-20251020-slim`, `11.11-slim`, `11-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/bullseye/slim/oci/index.json)
+-	[`bullseye-slim`, `bullseye-20251020-slim`, `11.11-slim`, `11-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/bullseye/slim/oci/index.json)
 
--	[`experimental`, `experimental-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/experimental/Dockerfile)
+-	[`experimental`, `experimental-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/experimental/Dockerfile)
 
--	[`forky`, `forky-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/forky/oci/index.json)
+-	[`forky`, `forky-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/forky/oci/index.json)
 
--	[`forky-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/forky/backports/Dockerfile)
+-	[`forky-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/forky/backports/Dockerfile)
 
--	[`forky-slim`, `forky-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/forky/slim/oci/index.json)
+-	[`forky-slim`, `forky-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/forky/slim/oci/index.json)
 
--	[`oldoldstable`, `oldoldstable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/oldoldstable/oci/index.json)
+-	[`oldoldstable`, `oldoldstable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/oldoldstable/oci/index.json)
 
--	[`oldoldstable-slim`, `oldoldstable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/oldoldstable/slim/oci/index.json)
+-	[`oldoldstable-slim`, `oldoldstable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/oldoldstable/slim/oci/index.json)
 
--	[`oldstable`, `oldstable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/oldstable/oci/index.json)
+-	[`oldstable`, `oldstable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/oldstable/oci/index.json)
 
--	[`oldstable-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/oldstable/backports/Dockerfile)
+-	[`oldstable-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/oldstable/backports/Dockerfile)
 
--	[`oldstable-slim`, `oldstable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/oldstable/slim/oci/index.json)
+-	[`oldstable-slim`, `oldstable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/oldstable/slim/oci/index.json)
 
--	[`rc-buggy`, `rc-buggy-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/rc-buggy/Dockerfile)
+-	[`rc-buggy`, `rc-buggy-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/rc-buggy/Dockerfile)
 
--	[`sid`, `sid-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/sid/oci/index.json)
+-	[`sid`, `sid-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/sid/oci/index.json)
 
--	[`sid-slim`, `sid-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/sid/slim/oci/index.json)
+-	[`sid-slim`, `sid-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/sid/slim/oci/index.json)
 
--	[`stable`, `stable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/stable/oci/index.json)
+-	[`stable`, `stable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/stable/oci/index.json)
 
--	[`stable-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/stable/backports/Dockerfile)
+-	[`stable-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/stable/backports/Dockerfile)
 
--	[`stable-slim`, `stable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/stable/slim/oci/index.json)
+-	[`stable-slim`, `stable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/stable/slim/oci/index.json)
 
--	[`testing`, `testing-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/testing/oci/index.json)
+-	[`testing`, `testing-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/testing/oci/index.json)
 
--	[`testing-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/testing/backports/Dockerfile)
+-	[`testing-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/testing/backports/Dockerfile)
 
--	[`testing-slim`, `testing-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/testing/slim/oci/index.json)
+-	[`testing-slim`, `testing-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/testing/slim/oci/index.json)
 
--	[`trixie`, `trixie-20251020`, `13.1`, `13`, `latest`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/trixie/oci/index.json)
+-	[`trixie`, `trixie-20251020`, `13.1`, `13`, `latest`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/trixie/oci/index.json)
 
--	[`trixie-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/trixie/backports/Dockerfile)
+-	[`trixie-backports`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/trixie/backports/Dockerfile)
 
--	[`trixie-slim`, `trixie-20251020-slim`, `13.1-slim`, `13-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/trixie/slim/oci/index.json)
+-	[`trixie-slim`, `trixie-20251020-slim`, `13.1-slim`, `13-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/trixie/slim/oci/index.json)
 
--	[`unstable`, `unstable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/unstable/oci/index.json)
+-	[`unstable`, `unstable-20251020`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/unstable/oci/index.json)
 
--	[`unstable-slim`, `unstable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/3b7829b548d4836ed5eb59d065d5f47d50a27edb/unstable/slim/oci/index.json)
+-	[`unstable-slim`, `unstable-20251020-slim`](https://github.com/debuerreotype/docker-debian-artifacts/blob/e68a1df9e902d926a7358a4f8076994438dd3a10/unstable/slim/oci/index.json)
 
 # Quick reference (cont.)
 
@@ -111,9 +113,9 @@ Debian is an operating system which is composed primarily of free and open-sourc
 
 The images in this repository are intended to be as minimal as possible (because of the immutable/layered nature of containers, it's much easier to add than it is to remove). More specifically, they're built from [the "minbase" variant](https://manpages.debian.org/stable/debootstrap/debootstrap.8.en.html#variant=minbase_buildd_fakechroot), which only installs "required" packages, and thus creates the smallest possible footprint that is still "Debian" (as defined/managed by [the Release and FTP teams](https://www.debian.org/intro/organization#distribution) within the project).
 
-The `debian:latest` tag will always point the latest stable release. Stable releases are also tagged with their version (ie, `debian:11` is an alias for `debian:bullseye`, `debian:10` is an alias for `debian:buster`, etc).
+The `arm64v8/debian:latest` tag will always point the latest stable release. Stable releases are also tagged with their version (ie, `arm64v8/debian:11` is an alias for `arm64v8/debian:bullseye`, `arm64v8/debian:10` is an alias for `arm64v8/debian:buster`, etc).
 
-The rolling tags (`debian:stable`, `debian:testing`, etc) use the rolling suite names in their `/etc/apt/sources.list` file (ie, `deb http://deb.debian.org/debian testing main`).
+The rolling tags (`arm64v8/debian:stable`, `arm64v8/debian:testing`, etc) use the rolling suite names in their `/etc/apt/sources.list` file (ie, `deb http://deb.debian.org/debian testing main`).
 
 The mirror of choice for these images is [the deb.debian.org CDN pointer/redirector](https://deb.debian.org) so that it's as reliable as possible for the largest subset of users (and is also the default mirror for `debootstrap` as of [2016-10-20](https://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=9e8bc60ad1ccf3a25ce7890526b70059f3e770de)). See the [deb.debian.org homepage](https://deb.debian.org) for more information.
 
@@ -141,7 +143,7 @@ For convenience, the SHA256 checksum (and full build command) for each of the pr
 
 # Image Variants
 
-## `debian:<suite>-slim`
+## `arm64v8/debian:<suite>-slim`
 
 These tags are an experiment in providing a slimmer base (removing some extra files that are normally not necessary within containers, such as man pages and documentation), and are definitely subject to change.
 

docker/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `docker` official image](https://hub.docker.com/_/docker) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -34,32 +36,14 @@ WARNING:
 
 -	[`29.0.0-rc.1-dind-rootless`, `29-rc-dind-rootless`, `rc-dind-rootless`](https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/dind-rootless/Dockerfile)
 
--	[`29.0.0-rc.1-windowsservercore-ltsc2025`, `29-rc-windowsservercore-ltsc2025`, `rc-windowsservercore-ltsc2025`](https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`29.0.0-rc.1-windowsservercore-ltsc2022`, `29-rc-windowsservercore-ltsc2022`, `rc-windowsservercore-ltsc2022`](https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/windows/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`28.5.1-cli`, `28.5-cli`, `28-cli`, `cli`, `28.5.1-cli-alpine3.22`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/cli/Dockerfile)
 
 -	[`28.5.1-dind`, `28.5-dind`, `28-dind`, `dind`, `28.5.1-dind-alpine3.22`, `28.5.1`, `28.5`, `28`, `latest`, `28.5.1-alpine3.22`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/dind/Dockerfile)
 
 -	[`28.5.1-dind-rootless`, `28.5-dind-rootless`, `28-dind-rootless`, `dind-rootless`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/dind-rootless/Dockerfile)
 
--	[`28.5.1-windowsservercore-ltsc2025`, `28.5-windowsservercore-ltsc2025`, `28-windowsservercore-ltsc2025`, `windowsservercore-ltsc2025`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`28.5.1-windowsservercore-ltsc2022`, `28.5-windowsservercore-ltsc2022`, `28-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/windows/windowsservercore-ltsc2022/Dockerfile)
-
 ## Shared Tags
 
--	`29.0.0-rc.1-windowsservercore`, `29-rc-windowsservercore`, `rc-windowsservercore`:
-
-	-	[`29.0.0-rc.1-windowsservercore-ltsc2025`](https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`29.0.0-rc.1-windowsservercore-ltsc2022`](https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`28.5.1-windowsservercore`, `28.5-windowsservercore`, `28-windowsservercore`, `windowsservercore`:
-
-	-	[`28.5.1-windowsservercore-ltsc2025`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`28.5.1-windowsservercore-ltsc2022`](https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/windows/windowsservercore-ltsc2022/Dockerfile)
-
 # Quick reference (cont.)
 
 -	**Where to file issues**:  
@@ -113,7 +97,7 @@ Inside the directory specified by `DOCKER_TLS_CERTDIR`, the entrypoint scripts w
 
 In order to make use of this functionality from a "client" container, at least the `client` subdirectory of the `$DOCKER_TLS_CERTDIR` directory needs to be shared (as illustrated in the following examples).
 
-To disable this image behavior, simply override the container command or entrypoint to run `dockerd` directly (`... docker:dind dockerd ...` or `... --entrypoint dockerd docker:dind ...`).
+To disable this image behavior, simply override the container command or entrypoint to run `dockerd` directly (`... arm64v8/docker:dind dockerd ...` or `... --entrypoint dockerd arm64v8/docker:dind ...`).
 
 ## Start a daemon instance
 
@@ -123,7 +107,7 @@ $ docker run --privileged --name some-docker -d \
 	-e DOCKER_TLS_CERTDIR=/certs \
 	-v some-docker-certs-ca:/certs/ca \
 	-v some-docker-certs-client:/certs/client \
-	docker:dind
+	arm64v8/docker:dind
 ```
 
 **Note:** `--privileged` is required for Docker-in-Docker to function properly, but it should be used with care as it provides full access to the host environment, as explained [in the relevant section of the Docker documentation](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
@@ -134,7 +118,7 @@ $ docker run --privileged --name some-docker -d \
 $ docker run --rm --network some-network \
 	-e DOCKER_TLS_CERTDIR=/certs \
 	-v some-docker-certs-client:/certs/client:ro \
-	docker:latest version
+	arm64v8/docker:latest version
 Client: Docker Engine - Community
  Version:           18.09.8
  API version:       1.39
@@ -159,7 +143,7 @@ Server: Docker Engine - Community
 $ docker run -it --rm --network some-network \
 	-e DOCKER_TLS_CERTDIR=/certs \
 	-v some-docker-certs-client:/certs/client:ro \
-	docker:latest sh
+	arm64v8/docker:latest sh
 / # docker version
 Client: Docker Engine - Community
  Version:           18.09.8
@@ -185,7 +169,7 @@ Server: Docker Engine - Community
 $ docker run --rm --network some-network \
 	-e DOCKER_TLS_CERTDIR=/certs \
 	-v some-docker-certs-client:/certs/client:ro \
-	docker:latest info
+	arm64v8/docker:latest info
 Containers: 0
  Running: 0
  Paused: 0
@@ -237,7 +221,7 @@ WARNING: bridge-nf-call-ip6tables is disabled
 ```
 
 ```console
-$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock docker:latest version
+$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock arm64v8/docker:latest version
 Client: Docker Engine - Community
  Version:           18.09.8
  API version:       1.39
@@ -266,7 +250,7 @@ $ docker run --privileged --name some-docker -d \
 	-e DOCKER_TLS_CERTDIR=/certs \
 	-v some-docker-certs-ca:/certs/ca \
 	-v some-docker-certs-client:/certs/client \
-	docker:dind --storage-driver overlay2
+	arm64v8/docker:dind --storage-driver overlay2
 ```
 
 ## Runtime Settings Considerations
@@ -281,7 +265,7 @@ $ docker run --privileged --name some-docker -d \
 	--ulimit core=-1 \
 	--pids-limit -1 \
 	--oom-score-adj -500 \
-	docker:dind
+	arm64v8/docker:dind
 ```
 
 Some of these will not be supported based on the settings on the host's `dockerd`, such as `--ulimit nofile=-1`, giving errors that look like `error setting rlimit type 7: operation not permitted`, and some may inherit sane values from the host `dockerd` instance or may not apply for your usage of Docker-in-Docker (for example, you likely want to set `--oom-score-adj` to a value that's higher than `dockerd` on the host so that your Docker-in-Docker instance is killed before the host Docker instance is).
@@ -299,20 +283,20 @@ The Docker documentation is a good starting point for understanding the differen
 2.	Start your `docker` container like this:
 
 	```console
-	$ docker run --privileged --name some-docker -v /my/own/var-lib-docker:/var/lib/docker -d docker:dind
+	$ docker run --privileged --name some-docker -v /my/own/var-lib-docker:/var/lib/docker -d arm64v8/docker:dind
 	```
 
 The `-v /my/own/var-lib-docker:/var/lib/docker` part of the command mounts the `/my/own/var-lib-docker` directory from the underlying host system as `/var/lib/docker` inside the container, where Docker by default will write its data files.
 
 # Image Variants
 
-The `docker` images come in many flavors, each designed for a specific use case.
+The `arm64v8/docker` images come in many flavors, each designed for a specific use case.
 
-## `docker:<version>`
+## `arm64v8/docker:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `docker:<version>-rootless`
+## `arm64v8/docker:<version>-rootless`
 
 For more information about using the experimental "rootless" image variants, see [docker-library/docker#174](https://github.com/docker-library/docker/pull/174).
 
@@ -321,7 +305,7 @@ For more information about using the experimental "rootless" image variants, see
 Basic example usage:
 
 ```console
-$ docker run -d --name some-docker --privileged docker:dind-rootless
+$ docker run -d --name some-docker --privileged arm64v8/docker:dind-rootless
 $ docker logs --tail=3 some-docker # to verify the daemon has finished generating TLS certificates and is listening successfully
 time="xxx" level=info msg="Daemon has completed initialization"
 time="xxx" level=info msg="API listen on /run/user/1000/docker.sock"
@@ -334,7 +318,7 @@ $ docker exec -it some-docker docker-entrypoint.sh sh # using "docker-entrypoint
 To run with a different UID/GID than the one baked into the image, modify `/etc/passwd`, `/etc/group`, and filesystem permissions (especially for the `rootless` user's home directory) as appropriate; for example:
 
 ```dockerfile
-FROM docker:dind-rootless
+FROM arm64v8/docker:dind-rootless
 USER root
 RUN set -eux; \
 	sed -i -e 's/^rootless:x:1000:1000:/rootless:x:1234:5678:/' /etc/passwd; \
@@ -343,10 +327,6 @@ RUN set -eux; \
 USER rootless
 ```
 
-## `docker:<version>-windowsservercore`
-
-Unfortunately, Windows does not support nested containers, so this image variant only contains the client (intended for use against an existing Docker engine, ala `-v //./pipe/docker_engine://./pipe/docker_engine`).
-
 # License
 
 View [license information](https://github.com/docker/docker/blob/eb7b2ed6bbe3fbef588116d362ce595d6e35fc43/LICENSE) for the software contained in this image.

drupal/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `drupal` official image](https://hub.docker.com/_/drupal) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -152,13 +154,13 @@ Drupal is a free and open-source content-management framework written in PHP and
 The basic pattern for starting a `drupal` instance is:
 
 ```console
-$ docker run --name some-drupal -d drupal
+$ docker run --name some-drupal -d arm64v8/drupal
 ```
 
 If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:
 
 ```console
-$ docker run --name some-drupal -p 8080:80 -d drupal
+$ docker run --name some-drupal -p 8080:80 -d arm64v8/drupal
 ```
 
 Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browser.
@@ -212,7 +214,7 @@ There is consensus that `/var/www/html/modules`, `/var/www/html/profiles`, and `
 If using bind-mounts, one way to accomplish pre-seeding your local `sites` directory would be something like the following:
 
 ```console
-$ docker run --rm drupal tar -cC /var/www/html/sites . | tar -xC /path/on/host/sites
+$ docker run --rm arm64v8/drupal tar -cC /var/www/html/sites . | tar -xC /path/on/host/sites
 ```
 
 This can then be bind-mounted into a new container:
@@ -223,20 +225,20 @@ $ docker run --name some-drupal --network some-network -d \
 	-v /path/on/host/profiles:/var/www/html/profiles \
 	-v /path/on/host/sites:/var/www/html/sites \
 	-v /path/on/host/themes:/var/www/html/themes \
-	drupal
+	arm64v8/drupal
 ```
 
 Another solution using Docker Volumes:
 
 ```console
 $ docker volume create drupal-sites
-$ docker run --rm -v drupal-sites:/temporary/sites drupal cp -aRT /var/www/html/sites /temporary/sites
+$ docker run --rm -v drupal-sites:/temporary/sites arm64v8/drupal cp -aRT /var/www/html/sites /temporary/sites
 $ docker run --name some-drupal --network some-network -d \
 	-v drupal-modules:/var/www/html/modules \
 	-v drupal-profiles:/var/www/html/profiles \
 	-v drupal-sites:/var/www/html/sites \
 	-v drupal-themes:/var/www/html/themes \
-	drupal
+	arm64v8/drupal
 ```
 
 ## ... via [`docker compose`](https://github.com/docker/compose)
@@ -296,15 +298,15 @@ See [the "Running as an arbitrary user" section of the `php` image documentation
 
 # Image Variants
 
-The `drupal` images come in many flavors, each designed for a specific use case.
+The `arm64v8/drupal` images come in many flavors, each designed for a specific use case.
 
-## `drupal:<version>`
+## `arm64v8/drupal:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `drupal:<version>-fpm`
+## `arm64v8/drupal:<version>-fpm`
 
 This variant contains [PHP's FastCGI Process Manager (FPM)](https://www.php.net/fpm), which is the recommended FastCGI implementation for PHP.
 

eclipse-mosquitto/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `eclipse-mosquitto` official image](https://hub.docker.com/_/eclipse-mosquitto) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -74,7 +76,7 @@ It is suggested to mirror this structure for your local configuration.
 When running the image, the default configuration values are used. To use a custom configuration file, create your mosquitto.conf in `$PWD/mosquitto/config/mosquitto.conf`, then mount the config directory to `/mosquitto/config`.
 
 ```console
-$ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" eclipse-mosquitto
+$ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" arm64v8/eclipse-mosquitto
 ```
 
 Configuration can be changed to:
@@ -95,13 +97,13 @@ i.e. add the following to `mosquitto.conf`:
 Run a container using the new image:
 
 ```console
-$ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v /mosquitto/data -v /mosquitto/log eclipse-mosquitto
+$ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v /mosquitto/data -v /mosquitto/log arm64v8/eclipse-mosquitto
 ```
 
 or:
 
 ```console
-$ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v "$PWD/mosquitto/data:/mosquitto/data" -v "$PWD/mosquitto/log:/mosquitto/log" eclipse-mosquitto
+$ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v "$PWD/mosquitto/data:/mosquitto/data" -v "$PWD/mosquitto/log:/mosquitto/log" arm64v8/eclipse-mosquitto
 ```
 
 **Note**: if the mosquitto configuration (mosquitto.conf) was modified to use non-default ports, the docker run command will need to be updated to expose the ports that have been configured.
@@ -109,7 +111,7 @@ $ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v "$
 For example, if you use port 1883 and port 8080:
 
 ```console
-$ docker run -it -p 1883:1883 -p 8080:8080 -v "$PWD/mosquitto/config:/mosquitto/config" eclipse-mosquitto
+$ docker run -it -p 1883:1883 -p 8080:8080 -v "$PWD/mosquitto/config:/mosquitto/config" arm64v8/eclipse-mosquitto
 ```
 
 # License

eclipse-temurin/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `eclipse-temurin` official image](https://hub.docker.com/_/eclipse-temurin) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -28,12 +30,6 @@ WARNING:
 
 ## Simple Tags
 
--	[`8u462-b08-jdk-alpine-3.20`, `8-jdk-alpine-3.20`, `8-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/alpine/3.20/Dockerfile)
-
--	[`8u462-b08-jdk-alpine-3.21`, `8-jdk-alpine-3.21`, `8-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/alpine/3.21/Dockerfile)
-
--	[`8u462-b08-jdk-alpine-3.22`, `8-jdk-alpine-3.22`, `8-alpine-3.22`, `8u462-b08-jdk-alpine`, `8-jdk-alpine`, `8-alpine`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/alpine/3.22/Dockerfile)
-
 -	[`8u462-b08-jdk-jammy`, `8-jdk-jammy`, `8-jammy`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/ubuntu/jammy/Dockerfile)
 
 -	[`8u462-b08-jdk-noble`, `8-jdk-noble`, `8-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/ubuntu/noble/Dockerfile)
@@ -42,20 +38,6 @@ WARNING:
 
 -	[`8u462-b08-jdk-ubi9-minimal`, `8-jdk-ubi9-minimal`, `8-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/ubi/ubi9-minimal/Dockerfile)
 
--	[`8u462-b08-jdk-windowsservercore-ltsc2025`, `8-jdk-windowsservercore-ltsc2025`, `8-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`8u462-b08-jdk-nanoserver-ltsc2025`, `8-jdk-nanoserver-ltsc2025`, `8-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`8u462-b08-jdk-windowsservercore-ltsc2022`, `8-jdk-windowsservercore-ltsc2022`, `8-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`8u462-b08-jdk-nanoserver-ltsc2022`, `8-jdk-nanoserver-ltsc2022`, `8-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/nanoserver-ltsc2022/Dockerfile)
-
--	[`8u462-b08-jre-alpine-3.20`, `8-jre-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/alpine/3.20/Dockerfile)
-
--	[`8u462-b08-jre-alpine-3.21`, `8-jre-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/alpine/3.21/Dockerfile)
-
--	[`8u462-b08-jre-alpine-3.22`, `8-jre-alpine-3.22`, `8u462-b08-jre-alpine`, `8-jre-alpine`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/alpine/3.22/Dockerfile)
-
 -	[`8u462-b08-jre-jammy`, `8-jre-jammy`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/ubuntu/jammy/Dockerfile)
 
 -	[`8u462-b08-jre-noble`, `8-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/ubuntu/noble/Dockerfile)
@@ -64,20 +46,6 @@ WARNING:
 
 -	[`8u462-b08-jre-ubi9-minimal`, `8-jre-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/ubi/ubi9-minimal/Dockerfile)
 
--	[`8u462-b08-jre-windowsservercore-ltsc2025`, `8-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`8u462-b08-jre-nanoserver-ltsc2025`, `8-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`8u462-b08-jre-windowsservercore-ltsc2022`, `8-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`8u462-b08-jre-nanoserver-ltsc2022`, `8-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/nanoserver-ltsc2022/Dockerfile)
-
--	[`11.0.28_6-jdk-alpine-3.20`, `11-jdk-alpine-3.20`, `11-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/alpine/3.20/Dockerfile)
-
--	[`11.0.28_6-jdk-alpine-3.21`, `11-jdk-alpine-3.21`, `11-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/alpine/3.21/Dockerfile)
-
--	[`11.0.28_6-jdk-alpine-3.22`, `11-jdk-alpine-3.22`, `11-alpine-3.22`, `11.0.28_6-jdk-alpine`, `11-jdk-alpine`, `11-alpine`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/alpine/3.22/Dockerfile)
-
 -	[`11.0.28_6-jdk-jammy`, `11-jdk-jammy`, `11-jammy`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/ubuntu/jammy/Dockerfile)
 
 -	[`11.0.28_6-jdk-noble`, `11-jdk-noble`, `11-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/ubuntu/noble/Dockerfile)
@@ -86,20 +54,6 @@ WARNING:
 
 -	[`11.0.28_6-jdk-ubi9-minimal`, `11-jdk-ubi9-minimal`, `11-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/ubi/ubi9-minimal/Dockerfile)
 
--	[`11.0.28_6-jdk-windowsservercore-ltsc2025`, `11-jdk-windowsservercore-ltsc2025`, `11-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`11.0.28_6-jdk-nanoserver-ltsc2025`, `11-jdk-nanoserver-ltsc2025`, `11-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`11.0.28_6-jdk-windowsservercore-ltsc2022`, `11-jdk-windowsservercore-ltsc2022`, `11-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`11.0.28_6-jdk-nanoserver-ltsc2022`, `11-jdk-nanoserver-ltsc2022`, `11-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/nanoserver-ltsc2022/Dockerfile)
-
--	[`11.0.28_6-jre-alpine-3.20`, `11-jre-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/alpine/3.20/Dockerfile)
-
--	[`11.0.28_6-jre-alpine-3.21`, `11-jre-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/alpine/3.21/Dockerfile)
-
--	[`11.0.28_6-jre-alpine-3.22`, `11-jre-alpine-3.22`, `11.0.28_6-jre-alpine`, `11-jre-alpine`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/alpine/3.22/Dockerfile)
-
 -	[`11.0.28_6-jre-jammy`, `11-jre-jammy`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/ubuntu/jammy/Dockerfile)
 
 -	[`11.0.28_6-jre-noble`, `11-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/ubuntu/noble/Dockerfile)
@@ -108,20 +62,6 @@ WARNING:
 
 -	[`11.0.28_6-jre-ubi9-minimal`, `11-jre-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/ubi/ubi9-minimal/Dockerfile)
 
--	[`11.0.28_6-jre-windowsservercore-ltsc2025`, `11-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`11.0.28_6-jre-nanoserver-ltsc2025`, `11-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`11.0.28_6-jre-windowsservercore-ltsc2022`, `11-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`11.0.28_6-jre-nanoserver-ltsc2022`, `11-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/nanoserver-ltsc2022/Dockerfile)
-
--	[`17.0.16_8-jdk-alpine-3.20`, `17-jdk-alpine-3.20`, `17-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/alpine/3.20/Dockerfile)
-
--	[`17.0.16_8-jdk-alpine-3.21`, `17-jdk-alpine-3.21`, `17-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/alpine/3.21/Dockerfile)
-
--	[`17.0.16_8-jdk-alpine-3.22`, `17-jdk-alpine-3.22`, `17-alpine-3.22`, `17.0.16_8-jdk-alpine`, `17-jdk-alpine`, `17-alpine`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/alpine/3.22/Dockerfile)
-
 -	[`17.0.16_8-jdk-jammy`, `17-jdk-jammy`, `17-jammy`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/ubuntu/jammy/Dockerfile)
 
 -	[`17.0.16_8-jdk-noble`, `17-jdk-noble`, `17-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/ubuntu/noble/Dockerfile)
@@ -130,20 +70,6 @@ WARNING:
 
 -	[`17.0.16_8-jdk-ubi9-minimal`, `17-jdk-ubi9-minimal`, `17-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/ubi/ubi9-minimal/Dockerfile)
 
--	[`17.0.16_8-jdk-windowsservercore-ltsc2025`, `17-jdk-windowsservercore-ltsc2025`, `17-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`17.0.16_8-jdk-nanoserver-ltsc2025`, `17-jdk-nanoserver-ltsc2025`, `17-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`17.0.16_8-jdk-windowsservercore-ltsc2022`, `17-jdk-windowsservercore-ltsc2022`, `17-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`17.0.16_8-jdk-nanoserver-ltsc2022`, `17-jdk-nanoserver-ltsc2022`, `17-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/nanoserver-ltsc2022/Dockerfile)
-
--	[`17.0.16_8-jre-alpine-3.20`, `17-jre-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/alpine/3.20/Dockerfile)
-
--	[`17.0.16_8-jre-alpine-3.21`, `17-jre-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/alpine/3.21/Dockerfile)
-
--	[`17.0.16_8-jre-alpine-3.22`, `17-jre-alpine-3.22`, `17.0.16_8-jre-alpine`, `17-jre-alpine`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/alpine/3.22/Dockerfile)
-
 -	[`17.0.16_8-jre-jammy`, `17-jre-jammy`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/ubuntu/jammy/Dockerfile)
 
 -	[`17.0.16_8-jre-noble`, `17-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/ubuntu/noble/Dockerfile)
@@ -152,14 +78,6 @@ WARNING:
 
 -	[`17.0.16_8-jre-ubi9-minimal`, `17-jre-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/ubi/ubi9-minimal/Dockerfile)
 
--	[`17.0.16_8-jre-windowsservercore-ltsc2025`, `17-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`17.0.16_8-jre-nanoserver-ltsc2025`, `17-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`17.0.16_8-jre-windowsservercore-ltsc2022`, `17-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`17.0.16_8-jre-nanoserver-ltsc2022`, `17-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`21.0.8_9-jdk-alpine-3.20`, `21-jdk-alpine-3.20`, `21-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/alpine/3.20/Dockerfile)
 
 -	[`21.0.8_9-jdk-alpine-3.21`, `21-jdk-alpine-3.21`, `21-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/alpine/3.21/Dockerfile)
@@ -174,14 +92,6 @@ WARNING:
 
 -	[`21.0.8_9-jdk-ubi9-minimal`, `21-jdk-ubi9-minimal`, `21-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/ubi/ubi9-minimal/Dockerfile)
 
--	[`21.0.8_9-jdk-windowsservercore-ltsc2025`, `21-jdk-windowsservercore-ltsc2025`, `21-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`21.0.8_9-jdk-nanoserver-ltsc2025`, `21-jdk-nanoserver-ltsc2025`, `21-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`21.0.8_9-jdk-windowsservercore-ltsc2022`, `21-jdk-windowsservercore-ltsc2022`, `21-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`21.0.8_9-jdk-nanoserver-ltsc2022`, `21-jdk-nanoserver-ltsc2022`, `21-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`21.0.8_9-jre-alpine-3.20`, `21-jre-alpine-3.20`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/alpine/3.20/Dockerfile)
 
 -	[`21.0.8_9-jre-alpine-3.21`, `21-jre-alpine-3.21`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/alpine/3.21/Dockerfile)
@@ -196,14 +106,6 @@ WARNING:
 
 -	[`21.0.8_9-jre-ubi9-minimal`, `21-jre-ubi9-minimal`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/ubi/ubi9-minimal/Dockerfile)
 
--	[`21.0.8_9-jre-windowsservercore-ltsc2025`, `21-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`21.0.8_9-jre-nanoserver-ltsc2025`, `21-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`21.0.8_9-jre-windowsservercore-ltsc2022`, `21-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`21.0.8_9-jre-nanoserver-ltsc2022`, `21-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`25_36-jdk-alpine-3.21`, `25-jdk-alpine-3.21`, `25-alpine-3.21`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/alpine/3.21/Dockerfile)
 
 -	[`25_36-jdk-alpine-3.22`, `25-jdk-alpine-3.22`, `25-alpine-3.22`, `25_36-jdk-alpine`, `25-jdk-alpine`, `25-alpine`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/alpine/3.22/Dockerfile)
@@ -214,14 +116,6 @@ WARNING:
 
 -	[`25_36-jdk-ubi10-minimal`, `25-jdk-ubi10-minimal`, `25-ubi10-minimal`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/ubi/ubi10-minimal/Dockerfile)
 
--	[`25_36-jdk-windowsservercore-ltsc2025`, `25-jdk-windowsservercore-ltsc2025`, `25-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`25_36-jdk-nanoserver-ltsc2025`, `25-jdk-nanoserver-ltsc2025`, `25-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`25_36-jdk-windowsservercore-ltsc2022`, `25-jdk-windowsservercore-ltsc2022`, `25-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`25_36-jdk-nanoserver-ltsc2022`, `25-jdk-nanoserver-ltsc2022`, `25-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`25_36-jre-alpine-3.21`, `25-jre-alpine-3.21`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/alpine/3.21/Dockerfile)
 
 -	[`25_36-jre-alpine-3.22`, `25-jre-alpine-3.22`, `25_36-jre-alpine`, `25-jre-alpine`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/alpine/3.22/Dockerfile)
@@ -232,175 +126,47 @@ WARNING:
 
 -	[`25_36-jre-ubi10-minimal`, `25-jre-ubi10-minimal`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/ubi/ubi10-minimal/Dockerfile)
 
--	[`25_36-jre-windowsservercore-ltsc2025`, `25-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`25_36-jre-nanoserver-ltsc2025`, `25-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`25_36-jre-windowsservercore-ltsc2022`, `25-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`25_36-jre-nanoserver-ltsc2022`, `25-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/nanoserver-ltsc2022/Dockerfile)
-
 ## Shared Tags
 
 -	`8u462-b08-jdk`, `8-jdk`, `8`:
 
 	-	[`8u462-b08-jdk-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/ubuntu/noble/Dockerfile)
-	-	[`8u462-b08-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`8u462-b08-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`8u462-b08-jdk-windowsservercore`, `8-jdk-windowsservercore`, `8-windowsservercore`:
-
-	-	[`8u462-b08-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`8u462-b08-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`8u462-b08-jdk-nanoserver`, `8-jdk-nanoserver`, `8-nanoserver`:
-
-	-	[`8u462-b08-jdk-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`8u462-b08-jdk-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jdk/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`8u462-b08-jre`, `8-jre`:
 
 	-	[`8u462-b08-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/ubuntu/noble/Dockerfile)
-	-	[`8u462-b08-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`8u462-b08-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`8u462-b08-jre-windowsservercore`, `8-jre-windowsservercore`:
-
-	-	[`8u462-b08-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`8u462-b08-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`8u462-b08-jre-nanoserver`, `8-jre-nanoserver`:
-
-	-	[`8u462-b08-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`8u462-b08-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/8/jre/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`11.0.28_6-jdk`, `11-jdk`, `11`:
 
 	-	[`11.0.28_6-jdk-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/ubuntu/noble/Dockerfile)
-	-	[`11.0.28_6-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`11.0.28_6-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`11.0.28_6-jdk-windowsservercore`, `11-jdk-windowsservercore`, `11-windowsservercore`:
-
-	-	[`11.0.28_6-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`11.0.28_6-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`11.0.28_6-jdk-nanoserver`, `11-jdk-nanoserver`, `11-nanoserver`:
-
-	-	[`11.0.28_6-jdk-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`11.0.28_6-jdk-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jdk/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`11.0.28_6-jre`, `11-jre`:
 
 	-	[`11.0.28_6-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/ubuntu/noble/Dockerfile)
-	-	[`11.0.28_6-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`11.0.28_6-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`11.0.28_6-jre-windowsservercore`, `11-jre-windowsservercore`:
-
-	-	[`11.0.28_6-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`11.0.28_6-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`11.0.28_6-jre-nanoserver`, `11-jre-nanoserver`:
-
-	-	[`11.0.28_6-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`11.0.28_6-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/11/jre/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`17.0.16_8-jdk`, `17-jdk`, `17`:
 
 	-	[`17.0.16_8-jdk-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/ubuntu/noble/Dockerfile)
-	-	[`17.0.16_8-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`17.0.16_8-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`17.0.16_8-jdk-windowsservercore`, `17-jdk-windowsservercore`, `17-windowsservercore`:
-
-	-	[`17.0.16_8-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`17.0.16_8-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`17.0.16_8-jdk-nanoserver`, `17-jdk-nanoserver`, `17-nanoserver`:
-
-	-	[`17.0.16_8-jdk-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`17.0.16_8-jdk-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jdk/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`17.0.16_8-jre`, `17-jre`:
 
 	-	[`17.0.16_8-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/ubuntu/noble/Dockerfile)
-	-	[`17.0.16_8-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`17.0.16_8-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`17.0.16_8-jre-windowsservercore`, `17-jre-windowsservercore`:
-
-	-	[`17.0.16_8-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`17.0.16_8-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`17.0.16_8-jre-nanoserver`, `17-jre-nanoserver`:
-
-	-	[`17.0.16_8-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`17.0.16_8-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/17/jre/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`21.0.8_9-jdk`, `21-jdk`, `21`:
 
 	-	[`21.0.8_9-jdk-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/ubuntu/noble/Dockerfile)
-	-	[`21.0.8_9-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`21.0.8_9-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`21.0.8_9-jdk-windowsservercore`, `21-jdk-windowsservercore`, `21-windowsservercore`:
-
-	-	[`21.0.8_9-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`21.0.8_9-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`21.0.8_9-jdk-nanoserver`, `21-jdk-nanoserver`, `21-nanoserver`:
-
-	-	[`21.0.8_9-jdk-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`21.0.8_9-jdk-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jdk/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`21.0.8_9-jre`, `21-jre`:
 
 	-	[`21.0.8_9-jre-noble`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/ubuntu/noble/Dockerfile)
-	-	[`21.0.8_9-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`21.0.8_9-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`21.0.8_9-jre-windowsservercore`, `21-jre-windowsservercore`:
-
-	-	[`21.0.8_9-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`21.0.8_9-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`21.0.8_9-jre-nanoserver`, `21-jre-nanoserver`:
-
-	-	[`21.0.8_9-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`21.0.8_9-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/fc54f27893bb7c1ffb1d7eb82f2d22d7605e57bc/21/jre/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`25_36-jdk`, `25-jdk`, `25`, `latest`:
 
 	-	[`25_36-jdk-noble`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/ubuntu/noble/Dockerfile)
-	-	[`25_36-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`25_36-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`25_36-jdk-windowsservercore`, `25-jdk-windowsservercore`, `25-windowsservercore`:
-
-	-	[`25_36-jdk-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`25_36-jdk-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`25_36-jdk-nanoserver`, `25-jdk-nanoserver`, `25-nanoserver`:
-
-	-	[`25_36-jdk-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`25_36-jdk-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jdk/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`25_36-jre`, `25-jre`:
 
 	-	[`25_36-jre-noble`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/ubuntu/noble/Dockerfile)
-	-	[`25_36-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`25_36-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`25_36-jre-windowsservercore`, `25-jre-windowsservercore`:
-
-	-	[`25_36-jre-windowsservercore-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`25_36-jre-windowsservercore-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`25_36-jre-nanoserver`, `25-jre-nanoserver`:
-
-	-	[`25_36-jre-nanoserver-ltsc2025`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`25_36-jre-nanoserver-ltsc2022`](https://github.com/adoptium/containers/blob/7fd47fcdc91108218327496869ec8d2f441eebb7/25/jre/windows/nanoserver-ltsc2022/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -442,7 +208,7 @@ Yes, it's possible for all image flavors except for Windows-based images. The fo
 You need to put your CA certificates into `/certificates` directory inside the container (e.g. by using a volume) and opt-in into CA certificate processing by setting the environment variable `USE_SYSTEM_CA_CERTS` on the container to any value (if you are overriding the entrypoint script, please make sure you call `/__cacert_entrypoint.sh` to enable the processing). Using Docker CLI this might look like this:
 
 ```console
-$ docker run -v $(pwd)/certs:/certificates/ -e USE_SYSTEM_CA_CERTS=1 eclipse-temurin:21
+$ docker run -v $(pwd)/certs:/certificates/ -e USE_SYSTEM_CA_CERTS=1 arm64v8/eclipse-temurin:21
 ```
 
 When run like this, your certificates will get added to both the JVM truststore and to the system CA store (e.g. for use by `curl` and other CLI tools). However, if you are running your containers in a restricted-by-default environment (such as Red Hat OpenShift), there will be some small differences:
@@ -458,7 +224,7 @@ While this feature has been tested in multiple scenarios, there is always a chan
 To run a pre-built jar file with the latest OpenJDK 21, use the following Dockerfile:
 
 ```dockerfile
-FROM eclipse-temurin:21
+FROM arm64v8/eclipse-temurin:21
 RUN mkdir /opt/app
 COPY japp.jar /opt/app
 CMD ["java", "-jar", "/opt/app/japp.jar"]
@@ -479,7 +245,7 @@ If you are using a distribution that we don't provide an image for you can copy
 # Example
 FROM <base image>
 ENV JAVA_HOME=/opt/java/openjdk
-COPY --from=eclipse-temurin:21 $JAVA_HOME $JAVA_HOME
+COPY --from=arm64v8/eclipse-temurin:21 $JAVA_HOME $JAVA_HOME
 ENV PATH="${JAVA_HOME}/bin:${PATH}"
 ```
 
@@ -489,7 +255,7 @@ On OpenJDK 21+, a JRE can be generated using `jlink`, see the following Dockerfi
 
 ```dockerfile
 # Example of custom Java runtime using jlink in a multi-stage container build
-FROM eclipse-temurin:21 as jre-build
+FROM arm64v8/eclipse-temurin:21 as jre-build
 
 # Create a custom Java runtime
 RUN $JAVA_HOME/bin/jlink \
@@ -515,7 +281,7 @@ CMD ["java", "-jar", "/opt/app/japp.jar"]
 If you want to place the jar file on the host file system instead of inside the container, you can mount the host path onto the container by using the following commands:
 
 ```dockerfile
-FROM eclipse-temurin:21.0.2_13-jdk
+FROM arm64v8/eclipse-temurin:21.0.2_13-jdk
 CMD ["java", "-jar", "/opt/app/japp.jar"]
 ```
 
@@ -526,15 +292,15 @@ docker run -it -v /path/on/host/system/jars:/opt/app japp
 
 # Image Variants
 
-The `eclipse-temurin` images come in many flavors, each designed for a specific use case.
+The `arm64v8/eclipse-temurin` images come in many flavors, each designed for a specific use case.
 
-## `eclipse-temurin:<version>`
+## `arm64v8/eclipse-temurin:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like jammy or noble in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
 
-## `eclipse-temurin:<version>-alpine`
+## `arm64v8/eclipse-temurin:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -542,14 +308,6 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `eclipse-temurin:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
 # License
 
 The Dockerfiles and associated scripts are licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).

eggdrop/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `eggdrop` official image](https://hub.docker.com/_/eggdrop) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -64,7 +66,7 @@ Eggdrop is the world's most popular Open Source IRC bot, designed for flexibilit
 To run this container the first time, you'll need to pass in, at minimum, a nickname and server via Environmental Variables. At minimum, a docker run command similar to
 
 ```console
-$ docker run -ti -e NICK=FooBot -e SERVER=irc.libera.chat -v /path/for/host/data:/home/eggdrop/eggdrop/data eggdrop
+$ docker run -ti -e NICK=FooBot -e SERVER=irc.libera.chat -v /path/for/host/data:/home/eggdrop/eggdrop/data arm64v8/eggdrop
 ```
 
 should be used. This will modify the appropriate values within the config file, then start your bot with the nickname FooBot and connect it to irc.libera.chat. These variables are only needed for your first run- after the first use, you can edit the config file directly. Additional configuration options are listed in the following sections.
@@ -118,13 +120,13 @@ If you use a config file from a previous eggdrop install (ie, you don't use the
 To do this, start your container with something similar to
 
 ```console
-$ docker run -i -e NICK=FooBot -e SERVER=irc.libera.chat -v /path/to/eggdrop/files:/home/eggdrop/eggdrop/data -d eggdrop
+$ docker run -i -e NICK=FooBot -e SERVER=irc.libera.chat -v /path/to/eggdrop/files:/home/eggdrop/eggdrop/data -d arm64v8/eggdrop
 ```
 
 If you provide your own config file, place it in the data dir and specify it as the argument to the docker container:
 
 ```console
-$ docker run -i -v /path/to/eggdrop/files:/home/eggdrop/eggdrop/data -d eggdrop mybot.conf
+$ docker run -i -v /path/to/eggdrop/files:/home/eggdrop/eggdrop/data -d arm64v8/eggdrop mybot.conf
 ```
 
 Any config file used with docker MUST end in .conf, such as eggdrop.conf or mybot.conf

elasticsearch/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `elasticsearch` official image](https://hub.docker.com/_/elasticsearch) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

elixir/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `elixir` official image](https://hub.docker.com/_/elixir) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -172,14 +174,14 @@ Elixir leverages the Erlang VM, known for running low-latency, distributed and f
 ## Run it as the REPL
 
 ```console
-➸ docker run -it --rm elixir
+➸ docker run -it --rm arm64v8/elixir
 Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
 
 Interactive Elixir (1.2.1) - press Ctrl+C to exit (type h() ENTER for help)
 iex(1)> System.version
 "1.2.1"
 iex(2)>
-➸ docker run -it --rm -h elixir.local elixir iex --sname snode
+➸ docker run -it --rm -h elixir.local arm64v8/elixir iex --sname snode
 Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
 
 Interactive Elixir (1.2.1) - press Ctrl+C to exit (type h() ENTER for help)
@@ -193,22 +195,22 @@ iex(snode@elixir)2> :c.uptime
 ## Run a single Elixir exs script
 
 ```console
-$ docker run -it --rm --name elixir-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp elixir elixir your-escript.exs
+$ docker run -it --rm --name elixir-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/elixir elixir your-escript.exs
 ```
 
 # Image Variants
 
-The `elixir` images come in many flavors, each designed for a specific use case.
+The `arm64v8/elixir` images come in many flavors, each designed for a specific use case.
 
-## `elixir:<version>`
+## `arm64v8/elixir:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `elixir:<version>-slim`
+## `arm64v8/elixir:<version>-slim`
 
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `elixir`. Unless you are working in an environment where *only* the `elixir` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/elixir`. Unless you are working in an environment where *only* the `arm64v8/elixir` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
 
-## `elixir:<version>-alpine`
+## `arm64v8/elixir:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

emqx/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `emqx` official image](https://hub.docker.com/_/emqx) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # **DEPRECATION NOTICE**
 
 Starting from v5.9.0, EMQX has unified all features from the previous Open Source and Enterprise editions into a single, powerful offering with the Business Source License (BSL) 1.1.
@@ -74,13 +76,13 @@ EMQX boasts more than 20K+ enterprise users across 50+ countries and regions, co
 Execute some command under this docker image
 
 ```console
-$ docker run -d --name emqx emqx:${tag}
+$ docker run -d --name emqx arm64v8/emqx:${tag}
 ```
 
 For example
 
 ```console
-$ docker run -d --name emqx -p 18083:18083 -p 1883:1883 emqx:latest
+$ docker run -d --name emqx -p 18083:18083 -p 1883:1883 arm64v8/emqx:latest
 ```
 
 The EMQX broker runs as Linux user `emqx` in the docker container.
@@ -104,7 +106,7 @@ Note: The lowercase use of 'default' is not a typo. It is used to demonstrate th
 For example, set MQTT TCP port to 1883
 
 ```console
-$ docker run -d --name emqx -e EMQX_DASHBOARD__DEFAULT_PASSWORD=mysecret -p 18083:18083 -p 1883:1883 emqx:latest
+$ docker run -d --name emqx -e EMQX_DASHBOARD__DEFAULT_PASSWORD=mysecret -p 18083:18083 -p 1883:1883 arm64v8/emqx:latest
 ```
 
 Please read more about EMQX configuration in the [official documentation](https://docs.emqx.com/en/emqx/latest/configuration/configuration.html)
@@ -126,7 +128,7 @@ Let's create a static node list cluster from Docker Compose.
 ```yaml
 services:
   emqx1:
-    image: emqx:latest
+    image: arm64v8/emqx:latest
     environment:
     - "[email protected]"
     - "EMQX_CLUSTER__DISCOVERY_STRATEGY=static"
@@ -137,7 +139,7 @@ services:
         - node1.emqx.io
 
   emqx2:
-    image: emqx:latest
+    image: arm64v8/emqx:latest
     environment:
     - "[email protected]"
     - "EMQX_CLUSTER__DISCOVERY_STRATEGY=static"
@@ -186,7 +188,7 @@ volumes:
 
 services:
   emqx:
-    image: emqx:latest
+    image: arm64v8/emqx:latest
     restart: always
     environment:
       EMQX_NODE__NAME: [email protected]
@@ -218,7 +220,7 @@ docker run -d --name emqx -p 18083:18083 -p 1883:1883 \
     --sysctl net.ipv4.tcp_wmem=1024 4096 16777216 \
     --sysctl net.ipv4.tcp_max_tw_buckets=1048576 \
     --sysctl net.ipv4.tcp_fin_timeout=15 \
-    emqx:latest
+    arm64v8/emqx:latest
 ```
 
 > REMEMBER: DO NOT RUN EMQX DOCKER PRIVILEGED OR MOUNT SYSTEM PROC IN CONTAINER TO TUNE LINUX KERNEL, IT IS UNSAFE.

erlang/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `erlang` official image](https://hub.docker.com/_/erlang) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -86,7 +88,7 @@ Erlang is a programming language used to build massively scalable soft real-time
 ## Run it as the REPL
 
 ```console
-➸ docker run -it --rm erlang
+➸ docker run -it --rm arm64v8/erlang
 Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]
 
 Eshell V9.0  (abort with ^G)
@@ -105,7 +107,7 @@ User switch command
   q                 - quit erlang
   ? | h             - this message
  --> q
-➸ docker run -it --rm -h erlang.local erlang erl -name [email protected]
+➸ docker run -it --rm -h erlang.local arm64v8/erlang erl -name [email protected]
 Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]
 
 Eshell V9.0  (abort with ^G)
@@ -119,24 +121,24 @@ User switch command
 ## Run a single Erlang escript
 
 ```console
-$ docker run -it --rm --name erlang-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp erlang escript your-escript.erl
+$ docker run -it --rm --name erlang-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/erlang escript your-escript.erl
 ```
 
 # Image Variants
 
-The `erlang` images come in many flavors, each designed for a specific use case.
+The `arm64v8/erlang` images come in many flavors, each designed for a specific use case.
 
-## `erlang:<version>`
+## `arm64v8/erlang:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
 
-## `erlang:<version>-slim`
+## `arm64v8/erlang:<version>-slim`
 
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `erlang`. Unless you are working in an environment where *only* the `erlang` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/erlang`. Unless you are working in an environment where *only* the `arm64v8/erlang` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
 
-## `erlang:<version>-alpine`
+## `arm64v8/erlang:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

fedora/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `fedora` official image](https://hub.docker.com/_/fedora) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,13 +26,13 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`41`](https://github.com/fedora-cloud/docker-brew-fedora/blob/fba75f9783b458ac342cc675892688169f6d5f9c/x86_64/Dockerfile)
+-	[`41`](https://github.com/fedora-cloud/docker-brew-fedora/blob/fba75f9783b458ac342cc675892688169f6d5f9c/aarch64/Dockerfile)
 
--	[`42`, `latest`](https://github.com/fedora-cloud/docker-brew-fedora/blob/b13b13dd4561da14a4de975c2ec754cb3fda5a27/x86_64/Dockerfile)
+-	[`42`, `latest`](https://github.com/fedora-cloud/docker-brew-fedora/blob/b13b13dd4561da14a4de975c2ec754cb3fda5a27/aarch64/Dockerfile)
 
--	[`43`](https://github.com/fedora-cloud/docker-brew-fedora/blob/d256792f0edba99d8c16d059c56709bff135a26b/x86_64/Dockerfile)
+-	[`43`](https://github.com/fedora-cloud/docker-brew-fedora/blob/d256792f0edba99d8c16d059c56709bff135a26b/aarch64/Dockerfile)
 
--	[`44`, `rawhide`](https://github.com/fedora-cloud/docker-brew-fedora/blob/7c36ff8d21c058cce31ee9e25f0c9c0537369c2f/x86_64/Dockerfile)
+-	[`44`, `rawhide`](https://github.com/fedora-cloud/docker-brew-fedora/blob/7c36ff8d21c058cce31ee9e25f0c9c0537369c2f/aarch64/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -57,11 +59,11 @@ This image serves as the `official Fedora image` for the [Fedora Distribution](h
 
 ![logo](https://raw.githubusercontent.com/docker-library/docs/7925a7131128930eed07077f9369b7ca52e0fd02/fedora/logo.png)
 
-The `fedora:latest` tag will always point to the latest stable release.
+The `arm64v8/fedora:latest` tag will always point to the latest stable release.
 
 This image is a relatively small footprint in comparison to a standard Fedora installation. This image is generated in the [Fedora Build System](http://koji.fedoraproject.org/koji/) and is built from [this kickstart file](https://pagure.io/fedora-kickstarts/blob/main/f/fedora-container-base.ks).
 
-[Fedora Rawhide](https://fedoraproject.org/wiki/Releases/Rawhide) is available via `fedora:rawhide` and any specific version of Fedora as `fedora:$version` (example: `fedora:23`).
+[Fedora Rawhide](https://fedoraproject.org/wiki/Releases/Rawhide) is available via `arm64v8/fedora:rawhide` and any specific version of Fedora as `arm64v8/fedora:$version` (example: `arm64v8/fedora:23`).
 
 # License
 

flink/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `flink` official image](https://hub.docker.com/_/flink) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

fluentd/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `fluentd` official image](https://hub.docker.com/_/fluentd) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -60,7 +62,7 @@ For more information, check [official site](https://www.fluentd.org/) and [docum
 # How to run images
 
 ```bash
-$ docker run -p 24224:24224 -p 24224:24224/udp -u fluent -v /path/to/dir:/fluentd/log fluentd
+$ docker run -p 24224:24224 -p 24224:24224/udp -u fluent -v /path/to/dir:/fluentd/log arm64v8/fluentd
 2019-01-16 11:49:55 +0000 [info]: parsing config file is succeeded path="/fluentd/etc/fluent.conf"
 ...
 2019-01-16 11:58:27 +0000 [info]: #0 [input1] listening port port=24224 bind="0.0.0.0"

friendica/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `friendica` official image](https://hub.docker.com/_/friendica) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -82,7 +84,7 @@ You need at least one other mariadb/mysql-container to link it to Friendica.
 The apache image contains a webserver and exposes port 80. To start the container type:
 
 ```console
-$ docker run -d -p 8080:80 --network some-network friendica
+$ docker run -d -p 8080:80 --network some-network arm64v8/friendica
 ```
 
 Now you can access the Friendica installation wizard at http://localhost:8080/ from your host system.
@@ -92,7 +94,7 @@ Now you can access the Friendica installation wizard at http://localhost:8080/ f
 To use the fpm image you need an additional web server that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases you might want use another container or your host as proxy. If you use your host you can address your Friendica container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via `docker run --network <NAME> ...` or a `compose.yaml` file). In both cases you don't want to map the fpm port to you host.
 
 ```console
-$ docker run -d friendica:fpm
+$ docker run -d arm64v8/friendica:fpm
 ```
 
 As the fastCGI-Process is not capable of serving static files (style sheets, images, ...) the webserver needs access to these files. This can be achieved with the `volumes-from` option. You can find more information in the Docker Compose section.
@@ -190,7 +192,7 @@ Friendica:
 $ docker run -d \
   -v friendica-vol-1:/var/www/html \
   --network some-network
-  friendica
+  arm64v8/friendica
 ```
 
 Database:
@@ -277,7 +279,7 @@ Currently, this is only supported for `FRIENDICA_ADMIN_MAIL`, `MYSQL_DATABASE`,
 
 ## Updating to a newer version
 
-You have to pull the latest image from the hub (`docker pull friendica`). The stable branch gets checked at every startup and will get updated if no installation was found or a new image is used.
+You have to pull the latest image from the hub (`docker pull arm64v8/friendica`). The stable branch gets checked at every startup and will get updated if no installation was found or a new image is used.
 
 # Running this image with Docker Compose
 
@@ -305,7 +307,7 @@ services:
       - MYSQL_RANDOM_ROOT_PASSWORD=yes
 
   app:
-    image: friendica
+    image: arm64v8/friendica
     restart: always
     volumes:
       - friendica:/var/www/html
@@ -354,7 +356,7 @@ services:
       - MYSQL_RANDOM_ROOT_PASSWORD=yes
 
   app:
-    image: friendica:fpm
+    image: arm64v8/friendica:fpm
     restart: always
     volumes:
       - friendica:/var/www/html    
@@ -400,13 +402,13 @@ If you got any questions or problems using the image, please visit our [Github R
 
 # Image Variants
 
-The `friendica` images come in many flavors, each designed for a specific use case.
+The `arm64v8/friendica` images come in many flavors, each designed for a specific use case.
 
-## `friendica:<version>`
+## `arm64v8/friendica:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `friendica:<version>-alpine`
+## `arm64v8/friendica:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

gazebo/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `gazebo` official image](https://hub.docker.com/_/gazebo) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,7 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
-**No supported tags**
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -58,7 +60,7 @@ Robot simulation is an essential tool in every roboticist's toolbox. A well-desi
 ## Create a `Dockerfile` in your Gazebo project
 
 ```dockerfile
-FROM gazebo:gzserver8
+FROM arm64v8/gazebo:gzserver8
 # place here your application's setup specifics
 CMD [ "gzserver", "my-gazebo-app-args" ]
 ```
@@ -89,7 +91,7 @@ Gazebo uses the `~/.gazebo/` directory for storing logs, models and scene info.
 For example, if one wishes to use their own `.gazebo` folder that already resides in their local home directory, with a username of `ubuntu`, we can simple launch the container with an additional volume argument:
 
 ```console
-$ docker run -v "/home/ubuntu/.gazebo/:/root/.gazebo/" gazebo
+$ docker run -v "/home/ubuntu/.gazebo/:/root/.gazebo/" arm64v8/gazebo
 ```
 
 One thing to be careful about is that gzserver logs to files named `/root/.gazebo/server-<port>/*.log`, where `<port>` is the port number that server is listening on (11345 by default). If you run and mount multiple containers using the same default port and same host side directory, then they will collide and attempt writing to the same file. If you want to run multiple gzservers on the same docker host, then a bit more clever volume mounting of `~/.gazebo/` subfolders would be required.
@@ -109,13 +111,13 @@ In this short example, we'll spin up a new container running gazebo server, conn
 > First launch a gazebo server with a mounted volume for logging and name the container gazebo:
 
 ```console
-$ docker run -d -v="/tmp/.gazebo/:/root/.gazebo/" --name=gazebo gazebo
+$ docker run -d -v="/tmp/.gazebo/:/root/.gazebo/" --name=gazebo arm64v8/gazebo
 ```
 
 > Now open a new bash session in the container using the same entrypoint to configure the environment. Then download the double_pendulum model and load it into the simulation.
 
 ```console
-$ docker exec -it gazebo bash
+$ docker exec -it arm64v8/gazebo bash
 $ apt-get update && apt-get install -y curl
 $ curl -o double_pendulum.sdf http://models.gazebosim.org/double_pendulum_with_base/model-1_4.sdf
 $ gz model --model-name double_pendulum --spawn-file double_pendulum.sdf

gcc/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `gcc` official image](https://hub.docker.com/_/gcc) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -66,7 +68,7 @@ The GNU Compiler Collection (GCC) is a compiler system produced by the GNU Proje
 The most straightforward way to use this image is to use a gcc container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project:
 
 ```dockerfile
-FROM gcc:4.9
+FROM arm64v8/gcc:4.9
 COPY . /usr/src/myapp
 WORKDIR /usr/src/myapp
 RUN gcc -o myapp main.c
@@ -85,13 +87,13 @@ $ docker run -it --rm --name my-running-app my-gcc-app
 There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp gcc:4.9 gcc -o myapp myapp.c
+$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/gcc:4.9 gcc -o myapp myapp.c
 ```
 
 This will add your current directory, as a volume, to the container, set the working directory to the volume, and run the command `gcc -o myapp myapp.c.` This tells gcc to compile the code in `myapp.c` and output the executable to myapp. Alternatively, if you have a `Makefile`, you can instead run the `make` command inside your container:
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp gcc:4.9 make
+$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/gcc:4.9 make
 ```
 
 # License

geonetwork/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `geonetwork` official image](https://hub.docker.com/_/geonetwork) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -73,24 +75,24 @@ This is a quick example of how to get GeoNetwork 4.4 Latest up and running for d
 
 ```console
 docker pull elasticsearch:7.17.15
-docker pull geonetwork:4
+docker pull arm64v8/geonetwork:4
 
 docker network create gn-network
 
 docker run -d --name my-es-host --network gn-network -e "discovery.type=single-node" elasticsearch:7.17.15
-docker run --name geonetwork-host --network gn-network -e GN_CONFIG_PROPERTIES="-Des.host=my-es-host -Des.protocol=http -Des.port=9200 -Des.url=http://my-es-host:9200" -p 8080:8080 geonetwork:4
+docker run --name geonetwork-host --network gn-network -e GN_CONFIG_PROPERTIES="-Des.host=my-es-host -Des.protocol=http -Des.port=9200 -Des.url=http://my-es-host:9200" -p 8080:8080 arm64v8/geonetwork:4
 ```
 
 For GeoNetwork 4.2 Stable:
 
 ```console
 docker pull elasticsearch:7.17.15
-docker pull geonetwork:4.2
+docker pull arm64v8/geonetwork:4.2
 
 docker network create gn-network
 
 docker run -d --name my-es-host --network gn-network -e "discovery.type=single-node" elasticsearch:7.17.15
-docker run --name geonetwork-host --network gn-network -e ES_HOST=my-es-host -e ES_PROTOCOL=http  -e ES_PORT=9200 -p 8080:8080 geonetwork:4.2
+docker run --name geonetwork-host --network gn-network -e ES_HOST=my-es-host -e ES_PROTOCOL=http  -e ES_PORT=9200 -p 8080:8080 arm64v8/geonetwork:4.2
 ```
 
 To be sure about what Elasticsearch version to use you can check the [GeoNetwork documentation](https://docs.geonetwork-opensource.org/4.4/install-guide/installing-index/) for your GN version or the `es.version` property in the [`pom.xml`](https://github.com/geonetwork/core-geonetwork/blob/main/pom.xml#L1528C17-L1528C24) file of the GeoNetwork release used.
@@ -119,7 +121,7 @@ Example Docker Compose YAML snippet:
 ```yaml
 services:
   geonetwork:
-    image: geonetwork:4.4
+    image: arm64v8/geonetwork:4.4
     environment:
       GN_CONFIG_PROPERTIES: >-
         -Des.host=elasticsearch
@@ -160,7 +162,7 @@ By default GeoNetwork uses a local **H2 database** for demo use (this one is **n
 This command will start a debian-based container, running a Tomcat (GN 3) or Jetty (GN 4) web server, with a GeoNetwork WAR deployed on the server:
 
 ```console
-docker run --name some-geonetwork -d geonetwork
+docker run --name some-geonetwork -d arm64v8/geonetwork
 ```
 
 ### Publish port
@@ -168,7 +170,7 @@ docker run --name some-geonetwork -d geonetwork
 GeoNetwork listens on port `8080`. If you want to access the container at the host, **you must publish this port**. For instance, this, will redirect all the container traffic on port 8080, to the same port on the host:
 
 ```console
-docker run --name some-geonetwork -d -p 8080:8080 geonetwork
+docker run --name some-geonetwork -d -p 8080:8080 arm64v8/geonetwork
 ```
 
 Then, if you are running docker on Linux, you may access geonetwork at http://localhost:8080/geonetwork.
@@ -182,7 +184,7 @@ By default, GeoNetwork sets the data directory on `/opt/geonetwork/WEB-INF/data`
 Since version 4.4.0 the data directory needs to be configued using Java properties passed in the `GN_CONFIG_PROPERTIES` environment variable. For example:
 
 ```console
-docker run --name some-geonetwork -d -p 8080:8080  -e GN_CONFIG_PROPERTIES="-Dgeonetwork.dir=/catalogue-data" -e GEONETWORK_DB_NAME=/catalogue-data/db/gn geonetwork
+docker run --name some-geonetwork -d -p 8080:8080  -e GN_CONFIG_PROPERTIES="-Dgeonetwork.dir=/catalogue-data" -e GEONETWORK_DB_NAME=/catalogue-data/db/gn arm64v8/geonetwork
 ```
 
 ### Persisting data
@@ -192,13 +194,13 @@ To set the data directory to `/catalogue-data/data` and H2 database file to `/ca
 -	GeoNetwork 4.2 and older
 
 ```console
-docker run --name some-geonetwork -d -p 8080:8080 -e DATA_DIR=/catalogue-data/data -e GEONETWORK_DB_NAME=/catalogue-data/db/gn geonetwork:3
+docker run --name some-geonetwork -d -p 8080:8080 -e DATA_DIR=/catalogue-data/data -e GEONETWORK_DB_NAME=/catalogue-data/db/gn arm64v8/geonetwork:3
 ```
 
 -	Since GeoNetwork 4.4.0
 
 ```console
-docker run --name some-geonetwork -d -p 8080:8080  -e GN_CONFIG_PROPERTIES="-Dgeonetwork.dir=/catalogue-data" -e GEONETWORK_DB_NAME=/catalogue-data/db/gn geonetwork
+docker run --name some-geonetwork -d -p 8080:8080  -e GN_CONFIG_PROPERTIES="-Dgeonetwork.dir=/catalogue-data" -e GEONETWORK_DB_NAME=/catalogue-data/db/gn arm64v8/geonetwork
 ```
 
 If you want the data directory to live beyond restarts, or even destruction of the container, you can mount a directory from the docker engine's host into the container. - `-v /host/path:/path/to/data/directory`. For instance this, will mount the host directory `/host/geonetwork-docker` into `/catalogue-data` on the container:
@@ -206,13 +208,13 @@ If you want the data directory to live beyond restarts, or even destruction of t
 -	GeoNetwork 4.2 and older
 
 ```console
-docker run --name some-geonetwork -d -p 8080:8080 -e DATA_DIR=/catalogue-data/data -e GEONETWORK_DB_NAME=/catalogue-data/db/gn -v /host/geonetwork-docker:/catalogue-data geonetwork:3
+docker run --name some-geonetwork -d -p 8080:8080 -e DATA_DIR=/catalogue-data/data -e GEONETWORK_DB_NAME=/catalogue-data/db/gn -v /host/geonetwork-docker:/catalogue-data arm64v8/geonetwork:3
 ```
 
 -	GeoNetwork 4.4.0 and newer
 
 ```console
-docker run --name some-geonetwork -d -p 8080:8080  -e GN_CONFIG_PROPERTIES="-Dgeonetwork.dir=/catalogue-data" -e GEONETWORK_DB_NAME=/catalogue-data/db/gn -v /host/geonetwork-docker:/catalogue-data geonetwork
+docker run --name some-geonetwork -d -p 8080:8080  -e GN_CONFIG_PROPERTIES="-Dgeonetwork.dir=/catalogue-data" -e GEONETWORK_DB_NAME=/catalogue-data/db/gn -v /host/geonetwork-docker:/catalogue-data arm64v8/geonetwork
 ```
 
 ### ... via [`docker compose`](https://github.com/docker/compose)

ghost/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `ghost` official image](https://hub.docker.com/_/ghost) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -64,7 +66,7 @@ Ghost is an independent platform for publishing online by web and email newslett
 This will start a Ghost development instance listening on the default Ghost port of 2368.
 
 ```console
-$ docker run -d --name some-ghost -e NODE_ENV=development ghost
+$ docker run -d --name some-ghost -e NODE_ENV=development arm64v8/ghost
 ```
 
 ## Custom port
@@ -72,7 +74,7 @@ $ docker run -d --name some-ghost -e NODE_ENV=development ghost
 If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:
 
 ```console
-$ docker run -d --name some-ghost -e NODE_ENV=development -e url=http://localhost:3001 -p 3001:2368 ghost
+$ docker run -d --name some-ghost -e NODE_ENV=development -e url=http://localhost:3001 -p 3001:2368 arm64v8/ghost
 ```
 
 If all goes well, you'll be able to access your new site on `http://localhost:3001` and `http://localhost:3001/ghost` to access Ghost Admin (or `http://host-ip:3001` and `http://host-ip:3001/ghost`, respectively).
@@ -94,7 +96,7 @@ $ docker run -d \
 	-e database__connection__filename='/var/lib/ghost/content/data/ghost.db' \
 	-p 3001:2368 \
 	-v /path/to/ghost/blog:/var/lib/ghost/content \
-	ghost:alpine
+	arm64v8/ghost:alpine
 ```
 
 Note: `database__connection__filename` is only valid in development mode and is the location for the SQLite database file. If using development mode, it should be set to a writeable path within a persistent folder (bind mount or volume). It is not available in production mode because an external MySQL server is required (see the Docker Compose example below).
@@ -110,7 +112,7 @@ $ docker run -d \
 	-e database__connection__filename='/var/lib/ghost/content/data/ghost.db' \
 	-p 3001:2368 \
 	-v some-ghost-data:/var/lib/ghost/content \
-	ghost
+	arm64v8/ghost
 ```
 
 ## Configuration
@@ -118,7 +120,7 @@ $ docker run -d \
 All Ghost configuration parameters (such as `url`) can be specified via environment variables. See [the Ghost documentation](https://ghost.org/docs/concepts/config/#running-ghost-with-config-env-variables) for details about what configuration is allowed and how to convert a nested configuration key into the appropriate environment variable name:
 
 ```console
-$ docker run -d --name some-ghost -e NODE_ENV=development -e url=http://some-ghost.example.com ghost
+$ docker run -d --name some-ghost -e NODE_ENV=development -e url=http://some-ghost.example.com arm64v8/ghost
 ```
 
 (There are further configuration examples in the `compose.yaml` listed below.)
@@ -185,13 +187,13 @@ Run `docker compose up`, wait for it to initialize completely, and visit `http:/
 
 # Image Variants
 
-The `ghost` images come in many flavors, each designed for a specific use case.
+The `arm64v8/ghost` images come in many flavors, each designed for a specific use case.
 
-## `ghost:<version>`
+## `arm64v8/ghost:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `ghost:<version>-alpine`
+## `arm64v8/ghost:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

golang/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `golang` official image](https://hub.docker.com/_/golang) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -36,14 +38,6 @@ WARNING:
 
 -	[`1.25.3-alpine3.21`, `1.25-alpine3.21`, `1-alpine3.21`, `alpine3.21`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/alpine3.21/Dockerfile)
 
--	[`1.25.3-windowsservercore-ltsc2025`, `1.25-windowsservercore-ltsc2025`, `1-windowsservercore-ltsc2025`, `windowsservercore-ltsc2025`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`1.25.3-windowsservercore-ltsc2022`, `1.25-windowsservercore-ltsc2022`, `1-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`1.25.3-nanoserver-ltsc2025`, `1.25-nanoserver-ltsc2025`, `1-nanoserver-ltsc2025`, `nanoserver-ltsc2025`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`1.25.3-nanoserver-ltsc2022`, `1.25-nanoserver-ltsc2022`, `1-nanoserver-ltsc2022`, `nanoserver-ltsc2022`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`1.24.9-trixie`, `1.24-trixie`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/trixie/Dockerfile)
 
 -	[`1.24.9-bookworm`, `1.24-bookworm`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/bookworm/Dockerfile)
@@ -52,14 +46,6 @@ WARNING:
 
 -	[`1.24.9-alpine3.21`, `1.24-alpine3.21`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/alpine3.21/Dockerfile)
 
--	[`1.24.9-windowsservercore-ltsc2025`, `1.24-windowsservercore-ltsc2025`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`1.24.9-windowsservercore-ltsc2022`, `1.24-windowsservercore-ltsc2022`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`1.24.9-nanoserver-ltsc2025`, `1.24-nanoserver-ltsc2025`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`1.24.9-nanoserver-ltsc2022`, `1.24-nanoserver-ltsc2022`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`tip-20251011-trixie`, `tip-trixie`](https://github.com/docker-library/golang/blob/048aed45b0fab735c8157c9449d32a17ee88cf62/tip/trixie/Dockerfile)
 
 -	[`tip-20251011-bookworm`, `tip-bookworm`](https://github.com/docker-library/golang/blob/048aed45b0fab735c8157c9449d32a17ee88cf62/tip/bookworm/Dockerfile)
@@ -73,34 +59,10 @@ WARNING:
 -	`1.25.3`, `1.25`, `1`, `latest`:
 
 	-	[`1.25.3-trixie`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/trixie/Dockerfile)
-	-	[`1.25.3-windowsservercore-ltsc2025`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.25.3-windowsservercore-ltsc2022`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.25.3-windowsservercore`, `1.25-windowsservercore`, `1-windowsservercore`, `windowsservercore`:
-
-	-	[`1.25.3-windowsservercore-ltsc2025`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.25.3-windowsservercore-ltsc2022`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.25.3-nanoserver`, `1.25-nanoserver`, `1-nanoserver`, `nanoserver`:
-
-	-	[`1.25.3-nanoserver-ltsc2025`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`1.25.3-nanoserver-ltsc2022`](https://github.com/docker-library/golang/blob/fca8040176e4e0c3d409c87d58fd8a81b16f2429/1.25/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`1.24.9`, `1.24`:
 
 	-	[`1.24.9-trixie`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/trixie/Dockerfile)
-	-	[`1.24.9-windowsservercore-ltsc2025`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.24.9-windowsservercore-ltsc2022`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.24.9-windowsservercore`, `1.24-windowsservercore`:
-
-	-	[`1.24.9-windowsservercore-ltsc2025`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.24.9-windowsservercore-ltsc2022`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.24.9-nanoserver`, `1.24-nanoserver`:
-
-	-	[`1.24.9-nanoserver-ltsc2025`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`1.24.9-nanoserver-ltsc2022`](https://github.com/docker-library/golang/blob/411dd143e04f39d9664f81d5284d7dd55949dbde/1.24/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`tip-20251011`, `tip`:
 
@@ -142,7 +104,7 @@ Go (a.k.a., Golang) is a programming language first developed at Google. It is a
 The most straightforward way to use this image is to use a Go container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project (assuming it uses `go.mod` for dependency management):
 
 ```dockerfile
-FROM golang:1.25
+FROM arm64v8/golang:1.25
 
 WORKDIR /usr/src/app
 
@@ -168,13 +130,13 @@ $ docker run -it --rm --name my-running-app my-golang-app
 There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.25 go build -v
+$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/golang:1.25 go build -v
 ```
 
 This will add your current directory as a volume to the container, set the working directory to the volume, and run the command `go build` which will tell go to compile the project in the working directory and output the executable to `myapp`. Alternatively, if you have a `Makefile`, you can run the `make` command inside your container.
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.25 make
+$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/golang:1.25 make
 ```
 
 ## Cross-compile your app inside the Docker container
@@ -182,13 +144,13 @@ $ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.25 make
 If you need to compile your application for a platform other than `linux/amd64` (such as `windows/386`):
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp -e GOOS=windows -e GOARCH=386 golang:1.25 go build -v
+$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp -e GOOS=windows -e GOARCH=386 arm64v8/golang:1.25 go build -v
 ```
 
 Alternatively, you can build for multiple platforms at once:
 
 ```console
-$ docker run --rm -it -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.25 bash
+$ docker run --rm -it -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/golang:1.25 bash
 $ for GOOS in darwin linux; do
 >   for GOARCH in 386 amd64; do
 >     export GOOS GOARCH
@@ -203,15 +165,15 @@ If downloading your dependencies results in an error like "checksum mismatch", y
 
 # Image Variants
 
-The `golang` images come in many flavors, each designed for a specific use case.
+The `arm64v8/golang` images come in many flavors, each designed for a specific use case.
 
-## `golang:<version>`
+## `arm64v8/golang:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `golang:<version>-alpine`
+## `arm64v8/golang:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -221,15 +183,7 @@ The main caveat to note is that it does use [musl libc](https://musl.libc.org) i
 
 To minimize image size, additional related tools (such as `git`, `gcc`, or `bash`) are not included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar). See also [docker-library/golang#250 (comment)](https://github.com/docker-library/golang/issues/250#issuecomment-451201761) for a longer explanation.
 
-## `golang:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
-## `golang:<version>-tip`
+## `arm64v8/golang:<version>-tip`
 
 The term "tip" in the Go community is used to refer to the latest development branch ([a leftover convention from previously using `hg` for version control](https://github.com/golang/build/blob/6383021611af0e07cbf0a60222e066662557c796/cmd/coordinator/internal/legacydash/build.go#L313-L314)).
 

gradle/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `gradle` official image](https://hub.docker.com/_/gradle) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -52,8 +54,6 @@ WARNING:
 
 -	[`9.1.0-jdk17-jammy`, `9.1-jdk17-jammy`, `9-jdk17-jammy`, `jdk17-jammy`](https://github.com/gradle/docker-gradle/blob/557df3e9d316f5069672935faff5a4fe532e63a6/jdk17-jammy/Dockerfile)
 
--	[`9.1.0-jdk17-alpine`, `9.1-jdk17-alpine`, `9-jdk17-alpine`, `jdk17-alpine`](https://github.com/gradle/docker-gradle/blob/557df3e9d316f5069672935faff5a4fe532e63a6/jdk17-alpine/Dockerfile)
-
 -	[`9.1.0-jdk17-corretto`, `9.1-jdk17-corretto`, `9-jdk17-corretto`, `jdk17-corretto`, `9.1.0-jdk17-corretto-al2023`, `9.1-jdk17-corretto-al2023`, `9-jdk17-corretto-al2023`, `jdk17-corretto-al2023`](https://github.com/gradle/docker-gradle/blob/557df3e9d316f5069672935faff5a4fe532e63a6/jdk17-corretto/Dockerfile)
 
 -	[`9.1.0-jdk17-ubi`, `9.1-jdk17-ubi`, `9-jdk17-ubi`, `jdk17-ubi`, `9.1.0-jdk17-ubi-minimal`, `9.1-jdk17-ubi-minimal`, `9-jdk17-ubi-minimal`, `jdk17-ubi-minimal`](https://github.com/gradle/docker-gradle/blob/557df3e9d316f5069672935faff5a4fe532e63a6/jdk17-ubi9/Dockerfile)
@@ -88,8 +88,6 @@ WARNING:
 
 -	[`8.14.3-jdk17-jammy`, `8.14-jdk17-jammy`, `8-jdk17-jammy`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk17-jammy/Dockerfile)
 
--	[`8.14.3-jdk17-alpine`, `8.14-jdk17-alpine`, `8-jdk17-alpine`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk17-alpine/Dockerfile)
-
 -	[`8.14.3-jdk17-corretto`, `8.14-jdk17-corretto`, `8-jdk17-corretto`, `8.14.3-jdk17-corretto-al2023`, `8.14-jdk17-corretto-al2023`, `8-jdk17-corretto-al2023`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk17-corretto/Dockerfile)
 
 -	[`8.14.3-jdk17-ubi`, `8.14-jdk17-ubi`, `8-jdk17-ubi`, `8.14.3-jdk17-ubi-minimal`, `8.14-jdk17-ubi-minimal`, `8-jdk17-ubi-minimal`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk17-ubi9/Dockerfile)
@@ -100,8 +98,6 @@ WARNING:
 
 -	[`8.14.3-jdk11`, `8.14-jdk11`, `8-jdk11`, `jdk11`, `8.14.3-jdk11-jammy`, `8.14-jdk11-jammy`, `8-jdk11-jammy`, `jdk11-jammy`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk11-jammy/Dockerfile)
 
--	[`8.14.3-jdk11-alpine`, `8.14-jdk11-alpine`, `8-jdk11-alpine`, `jdk11-alpine`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk11-alpine/Dockerfile)
-
 -	[`8.14.3-jdk11-corretto`, `8.14-jdk11-corretto`, `8-jdk11-corretto`, `jdk11-corretto`, `8.14.3-jdk11-corretto-al2023`, `8.14-jdk11-corretto-al2023`, `8-jdk11-corretto-al2023`, `jdk11-corretto-al2023`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk11-corretto/Dockerfile)
 
 -	[`8.14.3-jdk11-ubi`, `8.14-jdk11-ubi`, `8-jdk11-ubi`, `jdk11-ubi`, `8.14.3-jdk11-ubi-minimal`, `8.14-jdk11-ubi-minimal`, `8-jdk11-ubi-minimal`, `jdk11-ubi-minimal`](https://github.com/gradle/docker-gradle/blob/23cd8c04ce29ecafdbb26fc064e5db3da663b5d8/jdk11-ubi9/Dockerfile)
@@ -120,8 +116,6 @@ WARNING:
 
 -	[`7.6.6-jdk17-jammy`, `7.6-jdk17-jammy`, `7-jdk17-jammy`, `7.6.6-jdk-jammy`, `7.6-jdk-jammy`, `7-jdk-jammy`, `7.6.6-jammy`, `7.6-jammy`, `7-jammy`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk17-jammy/Dockerfile)
 
--	[`7.6.6-jdk17-alpine`, `7.6-jdk17-alpine`, `7-jdk17-alpine`, `7.6.6-jdk-alpine`, `7.6-jdk-alpine`, `7-jdk-alpine`, `7.6.6-alpine`, `7.6-alpine`, `7-alpine`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk17-alpine/Dockerfile)
-
 -	[`7.6.6-jdk17-corretto`, `7.6-jdk17-corretto`, `7-jdk17-corretto`, `7.6.6-jdk17-corretto-al2023`, `7.6-jdk17-corretto-al2023`, `7-jdk17-corretto-al2023`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk17-corretto/Dockerfile)
 
 -	[`7.6.6-jdk17-ubi`, `7.6-jdk17-ubi`, `7-jdk17-ubi`, `7.6.6-jdk17-ubi-minimal`, `7.6-jdk17-ubi-minimal`, `7-jdk17-ubi-minimal`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk17-ubi9/Dockerfile)
@@ -132,8 +126,6 @@ WARNING:
 
 -	[`7.6.6-jdk11`, `7.6-jdk11`, `7-jdk11`, `7.6.6-jdk11-jammy`, `7.6-jdk11-jammy`, `7-jdk11-jammy`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk11-jammy/Dockerfile)
 
--	[`7.6.6-jdk11-alpine`, `7.6-jdk11-alpine`, `7-jdk11-alpine`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk11-alpine/Dockerfile)
-
 -	[`7.6.6-jdk11-corretto`, `7.6-jdk11-corretto`, `7-jdk11-corretto`, `7.6.6-jdk11-corretto-al2023`, `7.6-jdk11-corretto-al2023`, `7-jdk11-corretto-al2023`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk11-corretto/Dockerfile)
 
 -	[`7.6.6-jdk11-ubi`, `7.6-jdk11-ubi`, `7-jdk11-ubi`, `7.6.6-jdk11-ubi-minimal`, `7.6-jdk11-ubi-minimal`, `7-jdk11-ubi-minimal`](https://github.com/gradle/docker-gradle/blob/692045c708bc589ff8fa26fb083bdf1b23c0f8a5/jdk11-ubi9/Dockerfile)
@@ -146,8 +138,6 @@ WARNING:
 
 -	[`6.9.4-jdk11`, `6.9-jdk11`, `6-jdk11`, `6.9.4-jdk11-jammy`, `6.9-jdk11-jammy`, `6-jdk11-jammy`, `6.9.4-jdk`, `6.9-jdk`, `6-jdk`, `6.9.4`, `6.9`, `6`, `6.9.4-jdk-jammy`, `6.9-jdk-jammy`, `6-jdk-jammy`, `6.9.4-jammy`, `6.9-jammy`, `6-jammy`](https://github.com/gradle/docker-gradle/blob/89adc634c8c98e9c132935942ed75ffce1d862f1/jdk11-jammy/Dockerfile)
 
--	[`6.9.4-jdk11-alpine`, `6.9-jdk11-alpine`, `6-jdk11-alpine`, `6.9.4-jdk-alpine`, `6.9-jdk-alpine`, `6-jdk-alpine`, `6.9.4-alpine`, `6.9-alpine`, `6-alpine`](https://github.com/gradle/docker-gradle/blob/89adc634c8c98e9c132935942ed75ffce1d862f1/jdk11-alpine/Dockerfile)
-
 -	[`6.9.4-jdk11-corretto`, `6.9-jdk11-corretto`, `6-jdk11-corretto`, `6.9.4-jdk11-corretto-al2023`, `6.9-jdk11-corretto-al2023`, `6-jdk11-corretto-al2023`](https://github.com/gradle/docker-gradle/blob/89adc634c8c98e9c132935942ed75ffce1d862f1/jdk11-corretto/Dockerfile)
 
 -	[`6.9.4-jdk11-ubi`, `6.9-jdk11-ubi`, `6-jdk11-ubi`, `6.9.4-jdk11-ubi-minimal`, `6.9-jdk11-ubi-minimal`, `6-jdk11-ubi-minimal`](https://github.com/gradle/docker-gradle/blob/89adc634c8c98e9c132935942ed75ffce1d862f1/jdk11-ubi9/Dockerfile)
@@ -193,22 +183,22 @@ From your project directory:
 docker run --rm -u gradle \
   -v "$PWD":/home/gradle/project \
   -w /home/gradle/project \
-  gradle gradle <task>
+  arm64v8/gradle gradle <task>
 ```
 
 Replace `<task>` with your desired Gradle task, e.g., `build`.
 
 # Image Variants
 
-The `gradle` images come in many flavors, each designed for a specific use case.
+The `arm64v8/gradle` images come in many flavors, each designed for a specific use case.
 
-## `gradle:<version>`
+## `arm64v8/gradle:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like jammy or noble in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
 
-## `gradle:<version>-alpine`
+## `arm64v8/gradle:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

groovy/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `groovy` official image](https://hub.docker.com/_/groovy) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -30,12 +32,8 @@ WARNING:
 
 -	[`4.0.27-jdk17`, `4.0-jdk17`, `4-jdk17`, `jdk17`, `4.0.27-jdk17-noble`, `4.0-jdk17-noble`, `4-jdk17-noble`, `jdk17-noble`](https://github.com/groovy/docker-groovy/blob/5a3c63b31c157987812e0b7d7d510cf83490e259/jdk17/Dockerfile)
 
--	[`4.0.27-jdk17-alpine`, `4.0-jdk17-alpine`, `4-jdk17-alpine`, `jdk17-alpine`](https://github.com/groovy/docker-groovy/blob/5a3c63b31c157987812e0b7d7d510cf83490e259/jdk17-alpine/Dockerfile)
-
 -	[`4.0.27-jdk11`, `4.0-jdk11`, `4-jdk11`, `jdk11`, `4.0.27-jdk11-jammy`, `4.0-jdk11-jammy`, `4-jdk11-jammy`, `jdk11-jammy`, `4.0.27-jdk-jammy`, `4.0-jdk-jammy`, `4-jdk-jammy`, `jdk-jammy`, `4.0.27-jammy`, `4.0-jammy`, `4-jammy`, `jammy`](https://github.com/groovy/docker-groovy/blob/5a3c63b31c157987812e0b7d7d510cf83490e259/jdk11/Dockerfile)
 
--	[`4.0.27-jdk11-alpine`, `4.0-jdk11-alpine`, `4-jdk11-alpine`, `jdk11-alpine`](https://github.com/groovy/docker-groovy/blob/5a3c63b31c157987812e0b7d7d510cf83490e259/jdk11-alpine/Dockerfile)
-
 -	[`4.0.27-jdk8`, `4.0-jdk8`, `4-jdk8`, `jdk8`, `4.0.27-jdk8-jammy`, `4.0-jdk8-jammy`, `4-jdk8-jammy`, `jdk8-jammy`](https://github.com/groovy/docker-groovy/blob/5a3c63b31c157987812e0b7d7d510cf83490e259/jdk8/Dockerfile)
 
 # Quick reference (cont.)
@@ -73,7 +71,7 @@ Note that if you are mounting a volume and the uid running Docker is not `1000`,
 
 ## Running a Groovy script
 
-`docker run --rm -v "$PWD":/home/groovy/scripts -w /home/groovy/scripts groovy groovy <script> <script-args>`
+`docker run --rm -v "$PWD":/home/groovy/scripts -w /home/groovy/scripts arm64v8/groovy groovy <script> <script-args>`
 
 ## Reusing the Grapes cache
 
@@ -81,20 +79,20 @@ The local Grapes cache can be reused across containers by creating a volume and
 
 ```console
 docker volume create --name grapes-cache
-docker run --rm -it -v grapes-cache:/home/groovy/.groovy/grapes groovy
+docker run --rm -it -v grapes-cache:/home/groovy/.groovy/grapes arm64v8/groovy
 ```
 
 # Image Variants
 
-The `groovy` images come in many flavors, each designed for a specific use case.
+The `arm64v8/groovy` images come in many flavors, each designed for a specific use case.
 
-## `groovy:<version>`
+## `arm64v8/groovy:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like jammy or noble in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
 
-## `groovy:<version>-alpine`
+## `arm64v8/groovy:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

haproxy/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `haproxy` official image](https://hub.docker.com/_/haproxy) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -90,7 +92,7 @@ It is also worth checking out the [`examples/` directory from upstream](http://g
 ## Create a `Dockerfile`
 
 ```dockerfile
-FROM haproxy:2.3
+FROM arm64v8/haproxy:2.3
 COPY haproxy.cfg /usr/local/etc/haproxy/haproxy.cfg
 ```
 
@@ -119,7 +121,7 @@ You will need a kernel at [version 4.11 or newer](https://github.com/moby/moby/i
 ## Directly via bind mount
 
 ```console
-$ docker run -d --name my-running-haproxy -v /path/to/etc/haproxy:/usr/local/etc/haproxy:ro --sysctl net.ipv4.ip_unprivileged_port_start=0 haproxy:2.3
+$ docker run -d --name my-running-haproxy -v /path/to/etc/haproxy:/usr/local/etc/haproxy:ro --sysctl net.ipv4.ip_unprivileged_port_start=0 arm64v8/haproxy:2.3
 ```
 
 Note that your host's `/path/to/etc/haproxy` folder should be populated with a file named `haproxy.cfg`. If this configuration file refers to any other files within that folder then you should ensure that they also exist (e.g. template files such as `400.http`, `404.http`, and so forth). However, many minimal configurations do not require any supporting files.
@@ -136,15 +138,15 @@ The entrypoint script in the image checks for running the command `haproxy` and
 
 # Image Variants
 
-The `haproxy` images come in many flavors, each designed for a specific use case.
+The `arm64v8/haproxy` images come in many flavors, each designed for a specific use case.
 
-## `haproxy:<version>`
+## `arm64v8/haproxy:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `haproxy:<version>-alpine`
+## `arm64v8/haproxy:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

haskell/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `haskell` official image](https://hub.docker.com/_/haskell) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -86,7 +88,7 @@ Additionally, we aim to support the two most recent versions of Debian (`stable`
 Start an interactive interpreter session with `ghci`:
 
 ```console
-$ docker run -it --rm haskell:9
+$ docker run -it --rm arm64v8/haskell:9
 GHCi, version 9.0.1: http://www.haskell.org/ghc/  :? for help
 Prelude>
 ```
@@ -94,7 +96,7 @@ Prelude>
 Dockerize an application using `stack`:
 
 ```dockerfile
-FROM haskell:8.10
+FROM arm64v8/haskell:8.10
 RUN stack install --resolver lts-17.14 pandoc citeproc
 ENTRYPOINT ["pandoc"]
 ```
@@ -102,7 +104,7 @@ ENTRYPOINT ["pandoc"]
 Dockerize an application using `cabal`:
 
 ```dockerfile
-FROM haskell:8.10
+FROM arm64v8/haskell:8.10
 RUN cabal update && cabal install pandoc citeproc
 ENTRYPOINT ["pandoc"]
 ```
@@ -110,7 +112,7 @@ ENTRYPOINT ["pandoc"]
 Iteratively develop a Haskell application with a `Dockerfile` utilizing the build cache:
 
 ```dockerfile
-FROM haskell:8
+FROM arm64v8/haskell:8
 
 WORKDIR /opt/example
 
@@ -133,7 +135,7 @@ CMD ["example"]
 
 ### Considerations for `happy`, `alex`, etc
 
-Some packages that also act as build dependencies, such as `happy` and `alex`, are no longer included in this image (as of `haskell:8.2.2` & `haskell:8.4.3`). There is a bootstrapping problem where one or more of these tools may be assumed to be available. If you run in to an error about missing dependencies that are not explicitly called out in a Cabal package, you will need to explicitly mark them for installation.
+Some packages that also act as build dependencies, such as `happy` and `alex`, are no longer included in this image (as of `arm64v8/haskell:8.2.2` & `arm64v8/haskell:8.4.3`). There is a bootstrapping problem where one or more of these tools may be assumed to be available. If you run in to an error about missing dependencies that are not explicitly called out in a Cabal package, you will need to explicitly mark them for installation.
 
 ### Considerations for Stack
 
@@ -153,7 +155,7 @@ Compiler version mismatched, found ghc-8.4.3 (x86_64), but expected minor versio
 To install the correct GHC into /root/.stack/programs/x86_64-linux/, try running "stack setup" or use the "--install-ghc" flag.
 ```
 
-In this case, the GHC release in the `haskell` Docker image got ahead of the default Stack resolver expected version of GHC. As the output suggests, manually setting the resolver (typically via `stack.yml`) is the recommended approach.
+In this case, the GHC release in the `arm64v8/haskell` Docker image got ahead of the default Stack resolver expected version of GHC. As the output suggests, manually setting the resolver (typically via `stack.yml`) is the recommended approach.
 
 ```console
 Step 2/3 : RUN stack install --resolver ghc-8.4.3 pandoc
@@ -165,19 +167,19 @@ Updating package index Hackage (mirrored at https://s3.amazonaws.com/hackage.fpc
 Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
 ```
 
-The alternative to use `--install-ghc` doesn't make sense in a Docker image context, and hence the global `install-ghc` flag has been set to `false` (as of `haskell:8.2.2` & `haskell:8.4.3`) to avoid the default behavior of bootstrapping a new GHC in the container.
+The alternative to use `--install-ghc` doesn't make sense in a Docker image context, and hence the global `install-ghc` flag has been set to `false` (as of `arm64v8/haskell:8.2.2` & `arm64v8/haskell:8.4.3`) to avoid the default behavior of bootstrapping a new GHC in the container.
 
 # Image Variants
 
-The `haskell` images come in many flavors, each designed for a specific use case.
+The `arm64v8/haskell` images come in many flavors, each designed for a specific use case.
 
-## `haskell:<version>`
+## `arm64v8/haskell:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or bullseye in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `haskell:<version>-slim`
+## `arm64v8/haskell:<version>-slim`
 
 This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `ghc`, `cabal-install` and `stack`. In addition, [profiling support](https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/profiling.html) is not included which saves ~ 700MB of space.
 

haxe/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `haxe` official image](https://hub.docker.com/_/haxe) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -32,10 +34,6 @@ WARNING:
 
 -	[`4.3.7-bullseye`, `4.3-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.3/bullseye/Dockerfile)
 
--	[`4.3.7-windowsservercore-ltsc2025`, `4.3-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.3/windowsservercore-ltsc2025/Dockerfile)
-
--	[`4.3.7-windowsservercore-ltsc2022`, `4.3-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.3/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`4.3.7-alpine3.22`, `4.3-alpine3.22`, `4.3.7-alpine`, `4.3-alpine`](https://github.com/HaxeFoundation/docker-library-haxe/blob/29c1c10f60a3d5d96c92c23ed8d07f5393c962b5/4.3/alpine3.22/Dockerfile)
 
 -	[`4.3.7-alpine3.21`, `4.3-alpine3.21`](https://github.com/HaxeFoundation/docker-library-haxe/blob/29c1c10f60a3d5d96c92c23ed8d07f5393c962b5/4.3/alpine3.21/Dockerfile)
@@ -48,10 +46,6 @@ WARNING:
 
 -	[`5.0.0-preview.1-bullseye`, `5.0.0-bullseye`, `5.0-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/5.0/bullseye/Dockerfile)
 
--	[`5.0.0-preview.1-windowsservercore-ltsc2025`, `5.0.0-windowsservercore-ltsc2025`, `5.0-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/5.0/windowsservercore-ltsc2025/Dockerfile)
-
--	[`5.0.0-preview.1-windowsservercore-ltsc2022`, `5.0.0-windowsservercore-ltsc2022`, `5.0-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/5.0/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`5.0.0-preview.1-alpine3.22`, `5.0.0-preview.1-alpine`, `5.0.0-alpine3.22`, `5.0-alpine3.22`, `5.0.0-alpine`, `5.0-alpine`](https://github.com/HaxeFoundation/docker-library-haxe/blob/29c1c10f60a3d5d96c92c23ed8d07f5393c962b5/5.0/alpine3.22/Dockerfile)
 
 -	[`5.0.0-preview.1-alpine3.21`, `5.0.0-alpine3.21`, `5.0-alpine3.21`](https://github.com/HaxeFoundation/docker-library-haxe/blob/29c1c10f60a3d5d96c92c23ed8d07f5393c962b5/5.0/alpine3.21/Dockerfile)
@@ -64,30 +58,18 @@ WARNING:
 
 -	[`4.2.5-bullseye`, `4.2-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.2/bullseye/Dockerfile)
 
--	[`4.2.5-windowsservercore-ltsc2025`, `4.2-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.2/windowsservercore-ltsc2025/Dockerfile)
-
--	[`4.2.5-windowsservercore-ltsc2022`, `4.2-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.2/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`4.2.5-alpine3.20`, `4.2-alpine3.20`, `4.2.5-alpine`, `4.2-alpine`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.2/alpine3.20/Dockerfile)
 
 -	[`4.2.5-alpine3.19`, `4.2-alpine3.19`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.2/alpine3.19/Dockerfile)
 
 -	[`4.1.5-bullseye`, `4.1-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.1/bullseye/Dockerfile)
 
--	[`4.1.5-windowsservercore-ltsc2025`, `4.1-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.1/windowsservercore-ltsc2025/Dockerfile)
-
--	[`4.1.5-windowsservercore-ltsc2022`, `4.1-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.1/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`4.1.5-alpine3.20`, `4.1-alpine3.20`, `4.1.5-alpine`, `4.1-alpine`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.1/alpine3.20/Dockerfile)
 
 -	[`4.1.5-alpine3.19`, `4.1-alpine3.19`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.1/alpine3.19/Dockerfile)
 
 -	[`4.0.5-bullseye`, `4.0-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.0/bullseye/Dockerfile)
 
--	[`4.0.5-windowsservercore-ltsc2025`, `4.0-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.0/windowsservercore-ltsc2025/Dockerfile)
-
--	[`4.0.5-windowsservercore-ltsc2022`, `4.0-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.0/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`4.0.5-alpine3.20`, `4.0-alpine3.20`, `4.0.5-alpine`, `4.0-alpine`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.0/alpine3.20/Dockerfile)
 
 -	[`4.0.5-alpine3.19`, `4.0-alpine3.19`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.0/alpine3.19/Dockerfile)
@@ -97,57 +79,22 @@ WARNING:
 -	`4.3.7`, `4.3`, `latest`:
 
 	-	[`4.3.7-bookworm`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.3/bookworm/Dockerfile)
-	-	[`4.3.7-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.3/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.3.7-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.3/windowsservercore-ltsc2022/Dockerfile)
-
--	`4.3.7-windowsservercore`, `4.3-windowsservercore`:
-
-	-	[`4.3.7-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.3/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.3.7-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.3/windowsservercore-ltsc2022/Dockerfile)
 
 -	`5.0.0-preview.1`, `5.0.0`, `5.0`:
 
 	-	[`5.0.0-preview.1-bookworm`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/5.0/bookworm/Dockerfile)
-	-	[`5.0.0-preview.1-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/5.0/windowsservercore-ltsc2025/Dockerfile)
-	-	[`5.0.0-preview.1-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/5.0/windowsservercore-ltsc2022/Dockerfile)
-
--	`5.0.0-preview.1-windowsservercore`, `5.0.0-windowsservercore`, `5.0-windowsservercore`:
-
-	-	[`5.0.0-preview.1-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/5.0/windowsservercore-ltsc2025/Dockerfile)
-	-	[`5.0.0-preview.1-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/5.0/windowsservercore-ltsc2022/Dockerfile)
 
 -	`4.2.5`, `4.2`:
 
 	-	[`4.2.5-bookworm`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.2/bookworm/Dockerfile)
-	-	[`4.2.5-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.2/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.2.5-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.2/windowsservercore-ltsc2022/Dockerfile)
-
--	`4.2.5-windowsservercore`, `4.2-windowsservercore`:
-
-	-	[`4.2.5-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.2/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.2.5-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.2/windowsservercore-ltsc2022/Dockerfile)
 
 -	`4.1.5`, `4.1`:
 
 	-	[`4.1.5-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.1/bullseye/Dockerfile)
-	-	[`4.1.5-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.1/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.1.5-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.1/windowsservercore-ltsc2022/Dockerfile)
-
--	`4.1.5-windowsservercore`, `4.1-windowsservercore`:
-
-	-	[`4.1.5-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.1/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.1.5-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.1/windowsservercore-ltsc2022/Dockerfile)
 
 -	`4.0.5`, `4.0`:
 
 	-	[`4.0.5-bullseye`](https://github.com/HaxeFoundation/docker-library-haxe/blob/2636eee6b67d0c99730e4ab1d0d752d66809e3fa/4.0/bullseye/Dockerfile)
-	-	[`4.0.5-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.0/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.0.5-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.0/windowsservercore-ltsc2022/Dockerfile)
-
--	`4.0.5-windowsservercore`, `4.0-windowsservercore`:
-
-	-	[`4.0.5-windowsservercore-ltsc2025`](https://github.com/HaxeFoundation/docker-library-haxe/blob/4e5b49d4004e4996d1d405de45967da6d36bdd94/4.0/windowsservercore-ltsc2025/Dockerfile)
-	-	[`4.0.5-windowsservercore-ltsc2022`](https://github.com/HaxeFoundation/docker-library-haxe/blob/c0367972017a7b87845bf33477e29b1fe64ccc4a/4.0/windowsservercore-ltsc2022/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -189,7 +136,7 @@ This image ships a minimal Haxe toolkit:
 The most straightforward way to use this image is to use a Haxe container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project:
 
 ```dockerfile
-FROM haxe:3.4
+FROM arm64v8/haxe:3.4
 
 RUN mkdir -p /usr/src/app
 WORKDIR /usr/src/app
@@ -217,10 +164,10 @@ $ docker run -it --rm --name my-running-app my-haxe-app
 
 There are `onbuild` variants that include multiple `ONBUILD` triggers to perform all of the steps in the above Dockerfile, except there is no `CMD` instruction for running the compilation output.
 
-Rewriting the above Dockerfile with `haxe:3.4-onbuild`, we will get:
+Rewriting the above Dockerfile with `arm64v8/haxe:3.4-onbuild`, we will get:
 
 ```dockerfile
-FROM haxe:3.4-onbuild
+FROM arm64v8/haxe:3.4-onbuild
 
 # run the output when the container starts
 CMD ["neko", "Main.n"]
@@ -234,23 +181,15 @@ $ docker build -t my-haxe-app --build-arg BUILD_HXML=compile.hxml .
 
 # Image Variants
 
-The `haxe` images come in many flavors, each designed for a specific use case.
+The `arm64v8/haxe` images come in many flavors, each designed for a specific use case.
 
-## `haxe:<version>`
+## `arm64v8/haxe:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or bullseye in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `haxe:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
-## `haxe:<version>-alpine`
+## `arm64v8/haxe:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

hello-world/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `hello-world` official image](https://hub.docker.com/_/hello-world) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -28,24 +30,13 @@ WARNING:
 
 ## Simple Tags
 
--	[`linux`](https://github.com/docker-library/hello-world/blob/6930d60e10e81283a57be3ee3a2b5ca328a40304/amd64/hello-world/Dockerfile)
-
--	[`nanoserver-ltsc2025`](https://github.com/docker-library/hello-world/blob/08987c71f648c985f54be2a80bed4223cbd0723b/amd64/hello-world/nanoserver-ltsc2025/Dockerfile)
-
--	[`nanoserver-ltsc2022`](https://github.com/docker-library/hello-world/blob/c816763efda4774cc0c628dca3c7dbd93c099928/amd64/hello-world/nanoserver-ltsc2022/Dockerfile)
+-	[`linux`](https://github.com/docker-library/hello-world/blob/6930d60e10e81283a57be3ee3a2b5ca328a40304/arm64v8/hello-world/Dockerfile)
 
 ## Shared Tags
 
 -	`latest`:
 
-	-	[`linux`](https://github.com/docker-library/hello-world/blob/6930d60e10e81283a57be3ee3a2b5ca328a40304/amd64/hello-world/Dockerfile)
-	-	[`nanoserver-ltsc2025`](https://github.com/docker-library/hello-world/blob/08987c71f648c985f54be2a80bed4223cbd0723b/amd64/hello-world/nanoserver-ltsc2025/Dockerfile)
-	-	[`nanoserver-ltsc2022`](https://github.com/docker-library/hello-world/blob/c816763efda4774cc0c628dca3c7dbd93c099928/amd64/hello-world/nanoserver-ltsc2022/Dockerfile)
-
--	`nanoserver`:
-
-	-	[`nanoserver-ltsc2025`](https://github.com/docker-library/hello-world/blob/08987c71f648c985f54be2a80bed4223cbd0723b/amd64/hello-world/nanoserver-ltsc2025/Dockerfile)
-	-	[`nanoserver-ltsc2022`](https://github.com/docker-library/hello-world/blob/c816763efda4774cc0c628dca3c7dbd93c099928/amd64/hello-world/nanoserver-ltsc2022/Dockerfile)
+	-	[`linux`](https://github.com/docker-library/hello-world/blob/6930d60e10e81283a57be3ee3a2b5ca328a40304/arm64v8/hello-world/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -69,7 +60,7 @@ WARNING:
 # Example output
 
 ```console
-$ docker run hello-world
+$ docker run arm64v8/hello-world
 
 Hello from Docker!
 This message shows that your installation appears to be working correctly.
@@ -93,7 +84,7 @@ For more examples and ideas, visit:
  https://docs.docker.com/get-started/
 
 
-$ docker images hello-world
+$ docker images arm64v8/hello-world
 REPOSITORY    TAG       IMAGE ID       SIZE
 hello-world   latest    1b44b5a3e06a   10.07kB
 ```
@@ -104,7 +95,7 @@ hello-world   latest    1b44b5a3e06a   10.07kB
 
 This image is a prime example of using the [`scratch`](https://hub.docker.com/_/scratch/) image effectively. See [`hello.c`](https://github.com/docker-library/hello-world/blob/master/hello.c) in https://github.com/docker-library/hello-world for the source code of the `hello` binary included in this image.
 
-Because this image consists of nothing but a single static binary which prints some text to standard output, it can trivially be run as any arbitrary user (`docker run --user $RANDOM:$RANDOM hello-world`, for example).
+Because this image consists of nothing but a single static binary which prints some text to standard output, it can trivially be run as any arbitrary user (`docker run --user $RANDOM:$RANDOM arm64v8/hello-world`, for example).
 
 # License
 

hitch/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `hitch` official image](https://hub.docker.com/_/hitch) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -54,7 +56,7 @@ WARNING:
 Running a Hitch Docker container can be done by using the following command:
 
 ```console
-$ docker run --name=hitch -p 443:443 hitch
+$ docker run --name=hitch -p 443:443 arm64v8/hitch
 ```
 
 This container will expose port `443`, which is required for HTTPS traffic.
@@ -64,7 +66,7 @@ This container will expose port `443`, which is required for HTTPS traffic.
 Without any argument, the container will run `hitch --config=/etc/hitch/hitch.conf`. You can mount your own configuration file to replace the default one:
 
 ```console
-$ docker run -v /path/to/your/config/file:/etc/hitch/hitch.conf:ro hitch
+$ docker run -v /path/to/your/config/file:/etc/hitch/hitch.conf:ro arm64v8/hitch
 ```
 
 You can also change the path of the configuration file by setting the `HITCH_CONFIG_FILE` environment variable.
@@ -82,7 +84,7 @@ But you'll probably run your backend service in a separate container. In that ca
 Here's how you set the backend via a *command-line option*, assuming your backend is available through `backend.example.com` on port `8443`:
 
 ```console
-$ docker run hitch "--backend=[backend.example.com]:8443"
+$ docker run arm64v8/hitch "--backend=[backend.example.com]:8443"
 ```
 
 ## Setting the certificate
@@ -96,7 +98,7 @@ This certificate is only suited for testing. Using a bind mount, you can overrid
 Here's an example:
 
 ```console
-$ docker run -v /path/to/your/certificate:/etc/hitch/certs/default:ro hitch
+$ docker run -v /path/to/your/certificate:/etc/hitch/certs/default:ro arm64v8/hitch
 ```
 
 You can also override the [`pem-file`](https://github.com/varnish/hitch/blob/master/hitch.conf.man.rst#pem-file--string) configuration setting in your mounted configuration file.
@@ -106,7 +108,7 @@ If you prefer setting the certificate location on the command line, you can add
 Here's how you do this:
 
 ```console
-$ docker run hitch "--backend=[backend.example.com]:8443:/path/to/cert.pem"
+$ docker run arm64v8/hitch "--backend=[backend.example.com]:8443:/path/to/cert.pem"
 ```
 
 # License

httpd/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `httpd` official image](https://hub.docker.com/_/httpd) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -62,7 +64,7 @@ This image only contains Apache httpd with the defaults from upstream. There is
 ### Create a `Dockerfile` in your project
 
 ```dockerfile
-FROM httpd:2.4
+FROM arm64v8/httpd:2.4
 COPY ./public-html/ /usr/local/apache2/htdocs/
 ```
 
@@ -80,7 +82,7 @@ Visit http://localhost:8080 and you will see It works!
 If you don't want to include a `Dockerfile` in your project, it is sufficient to do the following:
 
 ```console
-$ docker run -dit --name my-apache-app -p 8080:80 -v "$PWD":/usr/local/apache2/htdocs/ httpd:2.4
+$ docker run -dit --name my-apache-app -p 8080:80 -v "$PWD":/usr/local/apache2/htdocs/ arm64v8/httpd:2.4
 ```
 
 ### Configuration
@@ -88,13 +90,13 @@ $ docker run -dit --name my-apache-app -p 8080:80 -v "$PWD":/usr/local/apache2/h
 To customize the configuration of the httpd server, first obtain the upstream default configuration from the container:
 
 ```console
-$ docker run --rm httpd:2.4 cat /usr/local/apache2/conf/httpd.conf > my-httpd.conf
+$ docker run --rm arm64v8/httpd:2.4 cat /usr/local/apache2/conf/httpd.conf > my-httpd.conf
 ```
 
 You can then `COPY` your custom configuration in as `/usr/local/apache2/conf/httpd.conf`:
 
 ```dockerfile
-FROM httpd:2.4
+FROM arm64v8/httpd:2.4
 COPY ./my-httpd.conf /usr/local/apache2/conf/httpd.conf
 ```
 
@@ -128,15 +130,15 @@ The previous steps should work well for development, but we recommend customizin
 
 # Image Variants
 
-The `httpd` images come in many flavors, each designed for a specific use case.
+The `arm64v8/httpd` images come in many flavors, each designed for a specific use case.
 
-## `httpd:<version>`
+## `arm64v8/httpd:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `httpd:<version>-alpine`
+## `arm64v8/httpd:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

hylang/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `hylang` official image](https://hub.docker.com/_/hylang) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -36,10 +38,6 @@ WARNING:
 
 -	[`1.1.0-python3.14-alpine3.21`, `1.1-python3.14-alpine3.21`, `1-python3.14-alpine3.21`, `python3.14-alpine3.21`, `1.1.0-alpine3.21`, `1.1-alpine3.21`, `1-alpine3.21`, `alpine3.21`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.14-alpine3.21)
 
--	[`1.1.0-python3.14-windowsservercore-ltsc2025`, `1.1-python3.14-windowsservercore-ltsc2025`, `1-python3.14-windowsservercore-ltsc2025`, `python3.14-windowsservercore-ltsc2025`, `1.1.0-windowsservercore-ltsc2025`, `1.1-windowsservercore-ltsc2025`, `1-windowsservercore-ltsc2025`, `windowsservercore-ltsc2025`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.14-windowsservercore-ltsc2025)
-
--	[`1.1.0-python3.14-windowsservercore-ltsc2022`, `1.1-python3.14-windowsservercore-ltsc2022`, `1-python3.14-windowsservercore-ltsc2022`, `python3.14-windowsservercore-ltsc2022`, `1.1.0-windowsservercore-ltsc2022`, `1.1-windowsservercore-ltsc2022`, `1-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.14-windowsservercore-ltsc2022)
-
 -	[`1.1.0-python3.13-trixie`, `1.1-python3.13-trixie`, `1-python3.13-trixie`, `python3.13-trixie`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-trixie)
 
 -	[`1.1.0-python3.13-bookworm`, `1.1-python3.13-bookworm`, `1-python3.13-bookworm`, `python3.13-bookworm`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-bookworm)
@@ -48,10 +46,6 @@ WARNING:
 
 -	[`1.1.0-python3.13-alpine3.21`, `1.1-python3.13-alpine3.21`, `1-python3.13-alpine3.21`, `python3.13-alpine3.21`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-alpine3.21)
 
--	[`1.1.0-python3.13-windowsservercore-ltsc2025`, `1.1-python3.13-windowsservercore-ltsc2025`, `1-python3.13-windowsservercore-ltsc2025`, `python3.13-windowsservercore-ltsc2025`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-windowsservercore-ltsc2025)
-
--	[`1.1.0-python3.13-windowsservercore-ltsc2022`, `1.1-python3.13-windowsservercore-ltsc2022`, `1-python3.13-windowsservercore-ltsc2022`, `python3.13-windowsservercore-ltsc2022`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-windowsservercore-ltsc2022)
-
 -	[`1.1.0-python3.12-trixie`, `1.1-python3.12-trixie`, `1-python3.12-trixie`, `python3.12-trixie`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.12-trixie)
 
 -	[`1.1.0-python3.12-bookworm`, `1.1-python3.12-bookworm`, `1-python3.12-bookworm`, `python3.12-bookworm`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.12-bookworm)
@@ -88,23 +82,15 @@ WARNING:
 
 -	[`1.1.0-pypy3.11-bookworm`, `1.1-pypy3.11-bookworm`, `1-pypy3.11-bookworm`, `pypy3.11-bookworm`, `1.1.0-pypy-bookworm`, `1.1-pypy-bookworm`, `1-pypy-bookworm`, `pypy-bookworm`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.pypy3.11-bookworm)
 
--	[`1.1.0-pypy3.11-windowsservercore-ltsc2025`, `1.1-pypy3.11-windowsservercore-ltsc2025`, `1-pypy3.11-windowsservercore-ltsc2025`, `pypy3.11-windowsservercore-ltsc2025`, `1.1.0-pypy-windowsservercore-ltsc2025`, `1.1-pypy-windowsservercore-ltsc2025`, `1-pypy-windowsservercore-ltsc2025`, `pypy-windowsservercore-ltsc2025`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.pypy3.11-windowsservercore-ltsc2025)
-
--	[`1.1.0-pypy3.11-windowsservercore-ltsc2022`, `1.1-pypy3.11-windowsservercore-ltsc2022`, `1-pypy3.11-windowsservercore-ltsc2022`, `pypy3.11-windowsservercore-ltsc2022`, `1.1.0-pypy-windowsservercore-ltsc2022`, `1.1-pypy-windowsservercore-ltsc2022`, `1-pypy-windowsservercore-ltsc2022`, `pypy-windowsservercore-ltsc2022`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.pypy3.11-windowsservercore-ltsc2022)
-
 ## Shared Tags
 
 -	`1.1.0-python3.14`, `1.1-python3.14`, `1-python3.14`, `python3.14`, `1.1.0`, `1.1`, `1`, `latest`:
 
 	-	[`1.1.0-python3.14-trixie`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.14-trixie)
-	-	[`1.1.0-python3.14-windowsservercore-ltsc2025`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.14-windowsservercore-ltsc2025)
-	-	[`1.1.0-python3.14-windowsservercore-ltsc2022`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.14-windowsservercore-ltsc2022)
 
 -	`1.1.0-python3.13`, `1.1-python3.13`, `1-python3.13`, `python3.13`:
 
 	-	[`1.1.0-python3.13-trixie`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-trixie)
-	-	[`1.1.0-python3.13-windowsservercore-ltsc2025`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-windowsservercore-ltsc2025)
-	-	[`1.1.0-python3.13-windowsservercore-ltsc2022`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.python3.13-windowsservercore-ltsc2022)
 
 -	`1.1.0-python3.12`, `1.1-python3.12`, `1-python3.12`, `python3.12`:
 
@@ -125,8 +111,6 @@ WARNING:
 -	`1.1.0-pypy3.11`, `1.1-pypy3.11`, `1-pypy3.11`, `pypy3.11`, `1.1.0-pypy`, `1.1-pypy`, `1-pypy`, `pypy`:
 
 	-	[`1.1.0-pypy3.11-trixie`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.pypy3.11-trixie)
-	-	[`1.1.0-pypy3.11-windowsservercore-ltsc2025`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.pypy3.11-windowsservercore-ltsc2025)
-	-	[`1.1.0-pypy3.11-windowsservercore-ltsc2022`](https://github.com/hylang/docker-hylang/blob/fed7ae62acf5651a05a296ab7396151e8182aa89/dockerfiles-generated/Dockerfile.pypy3.11-windowsservercore-ltsc2022)
 
 # Quick reference (cont.)
 
@@ -160,7 +144,7 @@ Hy (a.k.a., Hylang) is a dialect of the Lisp programming language designed to in
 ## Create a `Dockerfile` in your Hy project
 
 ```dockerfile
-FROM hylang:0.10
+FROM arm64v8/hylang:0.10
 COPY . /usr/src/myapp
 WORKDIR /usr/src/myapp
 CMD [ "hy", "./your-daemon-or-script.hy" ]
@@ -178,20 +162,20 @@ $ docker run -it --rm --name my-running-app my-hylang-app
 For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Hy script by using the Hy Docker image directly:
 
 ```console
-$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp hylang:0.10 hy your-daemon-or-script.hy
+$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/hylang:0.10 hy your-daemon-or-script.hy
 ```
 
 # Image Variants
 
-The `hylang` images come in many flavors, each designed for a specific use case.
+The `arm64v8/hylang` images come in many flavors, each designed for a specific use case.
 
-## `hylang:<version>`
+## `arm64v8/hylang:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `hylang:<version>-alpine`
+## `arm64v8/hylang:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -199,14 +183,6 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `hylang:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
 # License
 
 View [license information](https://github.com/hylang/hy/blob/master/LICENSE) for the software contained in this image.

ibm-semeru-runtimes/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `ibm-semeru-runtimes` official image](https://hub.docker.com/_/ibm-semeru-runtimes) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -158,7 +160,7 @@ The IBM Semeru Runtimes are free production-ready open source binaries built wit
 To run a pre-built japp.jar file with the latest OpenJDK 11, use the following Dockerfile:
 
 ```dockerfile
-FROM ibm-semeru-runtimes:open-11-jdk
+FROM arm64v8/ibm-semeru-runtimes:open-11-jdk
 RUN mkdir /opt/app
 COPY japp.jar /opt/app
 CMD ["java", "-jar", "/opt/app/japp.jar"]
@@ -179,7 +181,7 @@ If you are using a distribution that we don't provide an image for you can copy
 # Example
 FROM <base image>
 ENV JAVA_HOME=/opt/java/openjdk
-COPY --from=ibm-semeru-runtimes:open-11-jdk $JAVA_HOME $JAVA_HOME
+COPY --from=arm64v8/ibm-semeru-runtimes:open-11-jdk $JAVA_HOME $JAVA_HOME
 ENV PATH="${JAVA_HOME}/bin:${PATH}"
 ```
 

ibmjava/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `ibmjava` official image](https://hub.docker.com/_/ibmjava) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,11 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`8-jre`, `jre`, `8`, `latest`](https://github.com/ibmruntimes/ci.docker/blob/c02f788be741734c7c5aa45832f63a700bae3707/ibmjava/8/jre/ubuntu/Dockerfile)
-
--	[`8-sfj`, `sfj`](https://github.com/ibmruntimes/ci.docker/blob/c02f788be741734c7c5aa45832f63a700bae3707/ibmjava/8/sfj/ubuntu/Dockerfile)
-
--	[`8-sdk`, `sdk`](https://github.com/ibmruntimes/ci.docker/blob/c02f788be741734c7c5aa45832f63a700bae3707/ibmjava/8/sdk/ubuntu/Dockerfile)
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -94,7 +92,7 @@ ibmjava now has multi-arch support and so the exact same commands as below works
 To run a pre-built jar file with the JRE image, use the following commands:
 
 ```dockerfile
-FROM ibmjava:jre
+FROM arm64v8/ibmjava:jre
 RUN mkdir /opt/app
 COPY japp.jar /opt/app
 CMD ["java", "-jar", "/opt/app/japp.jar"]
@@ -110,7 +108,7 @@ docker run -it --rm japp
 If you want to place the jar file on the host file system instead of inside the container, you can mount the host path onto the container by using the following commands:
 
 ```dockerfile
-FROM ibmjava:jre
+FROM arm64v8/ibmjava:jre
 CMD ["java", "-jar", "/opt/app/japp.jar"]
 ```
 
@@ -126,7 +124,7 @@ IBM SDK, Java Technology Edition provides a feature called [Class data sharing](
 To enable class data sharing between JVMs that are running in different containers on the same host, a common location must be shared between containers. This requirement can be satisfied through the host or a data volume container. When enabled, class data sharing creates a named "class cache", which is a memory-mapped file, at the common location. This feature is enabled by passing the `-Xshareclasses` option to the JVM as shown in the following Dockerfile example:
 
 ```dockerfile
-FROM ibmjava:jre
+FROM arm64v8/ibmjava:jre
 RUN mkdir /opt/shareclasses
 RUN mkdir /opt/app
 COPY japp.jar /opt/app

influxdb/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `influxdb` official image](https://hub.docker.com/_/influxdb) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -28,26 +30,10 @@ WARNING:
 
 -	[`1.12-alpine`, `1.12.2-alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.12/alpine/Dockerfile)
 
--	[`1.12-data`, `1.12.2-data`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.12/data/Dockerfile)
-
--	[`1.12-data-alpine`, `1.12.2-data-alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.12/data/alpine/Dockerfile)
-
--	[`1.12-meta`, `1.12.2-meta`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.12/meta/Dockerfile)
-
--	[`1.12-meta-alpine`, `1.12.2-meta-alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.12/meta/alpine/Dockerfile)
-
 -	[`1.11`, `1.11.8`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.11/Dockerfile)
 
 -	[`1.11-alpine`, `1.11.8-alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.11/alpine/Dockerfile)
 
--	[`1.11-data`, `1.11.9-data`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.11/data/Dockerfile)
-
--	[`1.11-data-alpine`, `1.11.9-data-alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.11/data/alpine/Dockerfile)
-
--	[`1.11-meta`, `1.11.9-meta`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.11/meta/Dockerfile)
-
--	[`1.11-meta-alpine`, `1.11.9-meta-alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/1.11/meta/alpine/Dockerfile)
-
 -	[`2`, `2.7`, `2.7.12`, `latest`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/2.7/Dockerfile)
 
 -	[`2-alpine`, `2.7-alpine`, `2.7.12-alpine`, `alpine`](https://github.com/influxdata/influxdata-docker/blob/8b7d5a121e4a60e18c1ccb064ca9b6e4617c97aa/influxdb/2.7/alpine/Dockerfile)
@@ -118,7 +104,7 @@ Alternatively, you can use the following command to start InfluxDB 3 Core:
 docker run --rm -p 8181:8181 \
   -v $PWD/data:/var/lib/influxdb3/data \
   -v $PWD/plugins:/var/lib/influxdb3/plugins \
-  influxdb:3-core influxdb3 serve \
+  arm64v8/influxdb:3-core influxdb3 serve \
     --node-id=my-node-0 \
     --object-store=file \
     --data-dir=/var/lib/influxdb3/data \
@@ -148,16 +134,16 @@ Use the following tools with InfluxDB 3 Core:
 Customize your instance with available [server options](https://docs.influxdata.com/influxdb3/core/reference/clis/influxdb3/serve/):
 
 ```bash
-   docker run --rm influxdb:3-core influxdb3 serve --help
+   docker run --rm arm64v8/influxdb:3-core influxdb3 serve --help
 ```
 
 ## Available InfluxDB variants
 
--	`influxdb:3-core` - **Latest InfluxDB OSS** (InfluxDB 3 Core)
--	`influxdb:2` - Previous generation OSS (InfluxDB v2)
--	`influxdb:1.11` - InfluxDB v1
+-	`arm64v8/influxdb:3-core` - **Latest InfluxDB OSS** (InfluxDB 3 Core)
+-	`arm64v8/influxdb:2` - Previous generation OSS (InfluxDB v2)
+-	`arm64v8/influxdb:1.11` - InfluxDB v1
 
-### InfluxDB 3 Core (`influxdb:3-core`) - Latest OSS
+### InfluxDB 3 Core (`arm64v8/influxdb:3-core`) - Latest OSS
 
 -	**Latest generation** using object storage with the InfluxDB 3 storage engine, Apache Arrow, and DataFusion SQL
 -	Sub-10ms queries and unlimited cardinality
@@ -166,20 +152,20 @@ Customize your instance with available [server options](https://docs.influxdata.
 -	Designed for real-time monitoring and recent data
 -	Includes InfluxDB v1 and v2 compatibility APIs
 
-### InfluxDB v2 (`influxdb:2`)
+### InfluxDB v2 (`arm64v8/influxdb:2`)
 
 -	Built on the TSM storage engine
 -	Supports Flux query language
 -	Integrated UI and dashboards
 -	Includes v1 compatibility API that supports InfluxQL
 
-### InfluxDB v1 (`influxdb:1.11`)
+### InfluxDB v1 (`arm64v8/influxdb:1.11`)
 
 -	Built on the TSM storage engine
 -	Original version with InfluxQL query language
 -	Proven stability for existing deployments
 
-### InfluxDB 3 Enterprise (license required) (`influxdb:3-enterprise`)
+### InfluxDB 3 Enterprise (license required) (`arm64v8/influxdb:3-enterprise`)
 
 Adds unlimited data retention, compaction, clustering, and high availability to InfluxDB 3 Core.
 
@@ -187,8 +173,8 @@ For setup instructions, see the [InfluxDB 3 Enterprise installation documentatio
 
 ### InfluxDB v1 Enterprise (license required)
 
--	`influxdb:1.11-data` - Data nodes for clustering
--	`influxdb:1.11-meta` - Meta nodes for cluster coordination (port 8091)
+-	`arm64v8/influxdb:1.11-data` - Data nodes for clustering
+-	`arm64v8/influxdb:1.11-meta` - Meta nodes for cluster coordination (port 8091)
 
 For setup instructions, see the [InfluxDB v1 Enterprise Docker documentation](https://docs.influxdata.com/enterprise_influxdb/v1/introduction/installation/docker/).
 
@@ -216,7 +202,7 @@ docker run -d -p 8086:8086 \
   -e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
   -e DOCKER_INFLUXDB_INIT_ORG=my-org \
   -e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
-  influxdb:2
+  arm64v8/influxdb:2
 ```
 
 After the container starts, visit [http://localhost:8086](http://localhost:8086) to view the UI.
@@ -230,7 +216,7 @@ For detailed instructions, see the [InfluxDB v2 Docker Compose documentation](ht
 ```bash
 docker run -d -p 8086:8086 \
   -v $PWD:/var/lib/influxdb \
-  influxdb:1.11
+  arm64v8/influxdb:1.11
 ```
 
 This starts InfluxDB v1 with:
@@ -242,13 +228,13 @@ For more information, see the [InfluxDB v1 Docker documentation](https://docs.in
 
 # Image Variants
 
-The `influxdb` images come in many flavors, each designed for a specific use case.
+The `arm64v8/influxdb` images come in many flavors, each designed for a specific use case.
 
-## `influxdb:<version>`
+## `arm64v8/influxdb:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `influxdb:<version>-alpine`
+## `arm64v8/influxdb:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

irssi/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `irssi` official image](https://hub.docker.com/_/irssi) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -70,7 +72,7 @@ $ docker run -it --name my-running-irssi -e TERM -u $(id -u):$(id -g) \
     --log-driver=none \
     -v $HOME/.irssi:/home/user/.irssi:ro \
     -v /etc/localtime:/etc/localtime:ro \
-    irssi
+    arm64v8/irssi
 ```
 
 We specify `--log-driver=none` to avoid storing useless interactive terminal data.
@@ -81,22 +83,22 @@ On a Mac OS X system, run the same image using:
 $ docker run -it --name my-running-irssi -e TERM -u $(id -u):$(id -g) \
     --log-driver=none \
     -v $HOME/.irssi:/home/user/.irssi:ro \
-    irssi
+    arm64v8/irssi
 ```
 
 You omit `/etc/localtime` on Mac OS X because `boot2docker` doesn't use this file.
 
 # Image Variants
 
-The `irssi` images come in many flavors, each designed for a specific use case.
+The `arm64v8/irssi` images come in many flavors, each designed for a specific use case.
 
-## `irssi:<version>`
+## `arm64v8/irssi:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `irssi:<version>-alpine`
+## `arm64v8/irssi:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

jetty/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `jetty` official image](https://hub.docker.com/_/jetty) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,110 +26,58 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`9.4.58-jre8-alpine`, `9.4-jre8-alpine`, `9-jre8-alpine`, `9.4.58-jre8-alpine-eclipse-temurin`, `9.4-jre8-alpine-eclipse-temurin`, `9-jre8-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre8-alpine/Dockerfile)
-
 -	[`9.4.58-jre8`, `9.4-jre8`, `9-jre8`, `9.4.58-jre8-eclipse-temurin`, `9.4-jre8-eclipse-temurin`, `9-jre8-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre8/Dockerfile)
 
--	[`9.4.58-jre21-alpine`, `9.4-jre21-alpine`, `9-jre21-alpine`, `9.4.58-jre21-alpine-eclipse-temurin`, `9.4-jre21-alpine-eclipse-temurin`, `9-jre21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre21-alpine/Dockerfile)
-
 -	[`9.4.58-jre21`, `9.4-jre21`, `9-jre21`, `9.4.58-jre21-eclipse-temurin`, `9.4-jre21-eclipse-temurin`, `9-jre21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre21/Dockerfile)
 
--	[`9.4.58-jre17-alpine`, `9.4-jre17-alpine`, `9-jre17-alpine`, `9.4.58-jre17-alpine-eclipse-temurin`, `9.4-jre17-alpine-eclipse-temurin`, `9-jre17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre17-alpine/Dockerfile)
-
 -	[`9.4.58-jre17`, `9.4-jre17`, `9-jre17`, `9.4.58-jre17-eclipse-temurin`, `9.4-jre17-eclipse-temurin`, `9-jre17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre17/Dockerfile)
 
--	[`9.4.58-jre11-alpine`, `9.4-jre11-alpine`, `9-jre11-alpine`, `9.4.58-jre11-alpine-eclipse-temurin`, `9.4-jre11-alpine-eclipse-temurin`, `9-jre11-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre11-alpine/Dockerfile)
-
 -	[`9.4.58-jre11`, `9.4-jre11`, `9-jre11`, `9.4.58-jre11-eclipse-temurin`, `9.4-jre11-eclipse-temurin`, `9-jre11-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jre11/Dockerfile)
 
 -	[`9.4.58-jdk8`, `9.4-jdk8`, `9-jdk8`, `9.4.58-jdk8-eclipse-temurin`, `9.4-jdk8-eclipse-temurin`, `9-jdk8-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk8/Dockerfile)
 
--	[`9.4.58-jdk21-alpine`, `9.4-jdk21-alpine`, `9-jdk21-alpine`, `9.4.58-jdk21-alpine-eclipse-temurin`, `9.4-jdk21-alpine-eclipse-temurin`, `9-jdk21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk21-alpine/Dockerfile)
-
 -	[`9.4.58`, `9.4`, `9`, `9.4.58-jdk21`, `9.4-jdk21`, `9-jdk21`, `9.4.58-eclipse-temurin`, `9.4-eclipse-temurin`, `9-eclipse-temurin`, `9.4.58-jdk21-eclipse-temurin`, `9.4-jdk21-eclipse-temurin`, `9-jdk21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk21/Dockerfile)
 
--	[`9.4.58-jdk17-alpine`, `9.4-jdk17-alpine`, `9-jdk17-alpine`, `9.4.58-jdk17-alpine-eclipse-temurin`, `9.4-jdk17-alpine-eclipse-temurin`, `9-jdk17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk17-alpine/Dockerfile)
-
 -	[`9.4.58-jdk17`, `9.4-jdk17`, `9-jdk17`, `9.4.58-jdk17-eclipse-temurin`, `9.4-jdk17-eclipse-temurin`, `9-jdk17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk17/Dockerfile)
 
--	[`9.4.58-jdk11-alpine`, `9.4-jdk11-alpine`, `9-jdk11-alpine`, `9.4.58-jdk11-alpine-eclipse-temurin`, `9.4-jdk11-alpine-eclipse-temurin`, `9-jdk11-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk11-alpine/Dockerfile)
-
 -	[`9.4.58-jdk11`, `9.4-jdk11`, `9-jdk11`, `9.4.58-jdk11-eclipse-temurin`, `9.4-jdk11-eclipse-temurin`, `9-jdk11-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/eclipse-temurin/9.4/jdk11/Dockerfile)
 
--	[`12.1.1-jdk21-alpine`, `12.1-jdk21-alpine`, `12-jdk21-alpine`, `12.1.1-jdk21-alpine-eclipse-temurin`, `12.1-jdk21-alpine-eclipse-temurin`, `12-jdk21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/7b96e36d06c0c483e7febbb975b398d546fdd7e3/eclipse-temurin/12.1/jdk21-alpine/Dockerfile)
-
 -	[`12.1.1`, `12.1`, `12`, `12.1.1-jdk21`, `12.1-jdk21`, `12-jdk21`, `12.1.1-eclipse-temurin`, `12.1-eclipse-temurin`, `12-eclipse-temurin`, `12.1.1-jdk21-eclipse-temurin`, `12.1-jdk21-eclipse-temurin`, `12-jdk21-eclipse-temurin`, `latest`, `jdk21`](https://github.com/eclipse/jetty.docker/blob/7b96e36d06c0c483e7febbb975b398d546fdd7e3/eclipse-temurin/12.1/jdk21/Dockerfile)
 
--	[`12.1.1-jdk17-alpine`, `12.1-jdk17-alpine`, `12-jdk17-alpine`, `12.1.1-jdk17-alpine-eclipse-temurin`, `12.1-jdk17-alpine-eclipse-temurin`, `12-jdk17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/7b96e36d06c0c483e7febbb975b398d546fdd7e3/eclipse-temurin/12.1/jdk17-alpine/Dockerfile)
-
 -	[`12.1.1-jdk17`, `12.1-jdk17`, `12-jdk17`, `12.1.1-jdk17-eclipse-temurin`, `12.1-jdk17-eclipse-temurin`, `12-jdk17-eclipse-temurin`, `jdk17`](https://github.com/eclipse/jetty.docker/blob/7b96e36d06c0c483e7febbb975b398d546fdd7e3/eclipse-temurin/12.1/jdk17/Dockerfile)
 
--	[`12.0.27-jre21-alpine`, `12.0-jre21-alpine`, `12.0.27-jre21-alpine-eclipse-temurin`, `12.0-jre21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jre21-alpine/Dockerfile)
-
 -	[`12.0.27-jre21`, `12.0-jre21`, `12.0.27-jre21-eclipse-temurin`, `12.0-jre21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jre21/Dockerfile)
 
--	[`12.0.27-jre17-alpine`, `12.0-jre17-alpine`, `12.0.27-jre17-alpine-eclipse-temurin`, `12.0-jre17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jre17-alpine/Dockerfile)
-
 -	[`12.0.27-jre17`, `12.0-jre17`, `12.0.27-jre17-eclipse-temurin`, `12.0-jre17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jre17/Dockerfile)
 
--	[`12.0.27-jdk24-alpine`, `12.0-jdk24-alpine`, `12.0.27-jdk24-alpine-eclipse-temurin`, `12.0-jdk24-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jdk24-alpine/Dockerfile)
-
 -	[`12.0.27-jdk24`, `12.0-jdk24`, `12.0.27-jdk24-eclipse-temurin`, `12.0-jdk24-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jdk24/Dockerfile)
 
--	[`12.0.27-jdk21-alpine`, `12.0-jdk21-alpine`, `12.0.27-jdk21-alpine-eclipse-temurin`, `12.0-jdk21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jdk21-alpine/Dockerfile)
-
 -	[`12.0.27`, `12.0`, `12.0.27-jdk21`, `12.0-jdk21`, `12.0.27-eclipse-temurin`, `12.0-eclipse-temurin`, `12.0.27-jdk21-eclipse-temurin`, `12.0-jdk21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jdk21/Dockerfile)
 
--	[`12.0.27-jdk17-alpine`, `12.0-jdk17-alpine`, `12.0.27-jdk17-alpine-eclipse-temurin`, `12.0-jdk17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jdk17-alpine/Dockerfile)
-
 -	[`12.0.27-jdk17`, `12.0-jdk17`, `12.0.27-jdk17-eclipse-temurin`, `12.0-jdk17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/1f3921ec1c01e622d6ddb0f64f02fbf266e68312/eclipse-temurin/12.0/jdk17/Dockerfile)
 
--	[`11.0.26-jre21-alpine`, `11.0-jre21-alpine`, `11-jre21-alpine`, `11.0.26-jre21-alpine-eclipse-temurin`, `11.0-jre21-alpine-eclipse-temurin`, `11-jre21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jre21-alpine/Dockerfile)
-
 -	[`11.0.26-jre21`, `11.0-jre21`, `11-jre21`, `11.0.26-jre21-eclipse-temurin`, `11.0-jre21-eclipse-temurin`, `11-jre21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jre21/Dockerfile)
 
--	[`11.0.26-jre17-alpine`, `11.0-jre17-alpine`, `11-jre17-alpine`, `11.0.26-jre17-alpine-eclipse-temurin`, `11.0-jre17-alpine-eclipse-temurin`, `11-jre17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jre17-alpine/Dockerfile)
-
 -	[`11.0.26-jre17`, `11.0-jre17`, `11-jre17`, `11.0.26-jre17-eclipse-temurin`, `11.0-jre17-eclipse-temurin`, `11-jre17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jre17/Dockerfile)
 
--	[`11.0.26-jre11-alpine`, `11.0-jre11-alpine`, `11-jre11-alpine`, `11.0.26-jre11-alpine-eclipse-temurin`, `11.0-jre11-alpine-eclipse-temurin`, `11-jre11-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jre11-alpine/Dockerfile)
-
 -	[`11.0.26-jre11`, `11.0-jre11`, `11-jre11`, `11.0.26-jre11-eclipse-temurin`, `11.0-jre11-eclipse-temurin`, `11-jre11-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jre11/Dockerfile)
 
--	[`11.0.26-jdk21-alpine`, `11.0-jdk21-alpine`, `11-jdk21-alpine`, `11.0.26-jdk21-alpine-eclipse-temurin`, `11.0-jdk21-alpine-eclipse-temurin`, `11-jdk21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jdk21-alpine/Dockerfile)
-
 -	[`11.0.26`, `11.0`, `11`, `11.0.26-jdk21`, `11.0-jdk21`, `11-jdk21`, `11.0.26-eclipse-temurin`, `11.0-eclipse-temurin`, `11-eclipse-temurin`, `11.0.26-jdk21-eclipse-temurin`, `11.0-jdk21-eclipse-temurin`, `11-jdk21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jdk21/Dockerfile)
 
--	[`11.0.26-jdk17-alpine`, `11.0-jdk17-alpine`, `11-jdk17-alpine`, `11.0.26-jdk17-alpine-eclipse-temurin`, `11.0-jdk17-alpine-eclipse-temurin`, `11-jdk17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jdk17-alpine/Dockerfile)
-
 -	[`11.0.26-jdk17`, `11.0-jdk17`, `11-jdk17`, `11.0.26-jdk17-eclipse-temurin`, `11.0-jdk17-eclipse-temurin`, `11-jdk17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jdk17/Dockerfile)
 
--	[`11.0.26-jdk11-alpine`, `11.0-jdk11-alpine`, `11-jdk11-alpine`, `11.0.26-jdk11-alpine-eclipse-temurin`, `11.0-jdk11-alpine-eclipse-temurin`, `11-jdk11-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jdk11-alpine/Dockerfile)
-
 -	[`11.0.26-jdk11`, `11.0-jdk11`, `11-jdk11`, `11.0.26-jdk11-eclipse-temurin`, `11.0-jdk11-eclipse-temurin`, `11-jdk11-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/11.0/jdk11/Dockerfile)
 
--	[`10.0.26-jre21-alpine`, `10.0-jre21-alpine`, `10-jre21-alpine`, `10.0.26-jre21-alpine-eclipse-temurin`, `10.0-jre21-alpine-eclipse-temurin`, `10-jre21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jre21-alpine/Dockerfile)
-
 -	[`10.0.26-jre21`, `10.0-jre21`, `10-jre21`, `10.0.26-jre21-eclipse-temurin`, `10.0-jre21-eclipse-temurin`, `10-jre21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jre21/Dockerfile)
 
--	[`10.0.26-jre17-alpine`, `10.0-jre17-alpine`, `10-jre17-alpine`, `10.0.26-jre17-alpine-eclipse-temurin`, `10.0-jre17-alpine-eclipse-temurin`, `10-jre17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jre17-alpine/Dockerfile)
-
 -	[`10.0.26-jre17`, `10.0-jre17`, `10-jre17`, `10.0.26-jre17-eclipse-temurin`, `10.0-jre17-eclipse-temurin`, `10-jre17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jre17/Dockerfile)
 
--	[`10.0.26-jre11-alpine`, `10.0-jre11-alpine`, `10-jre11-alpine`, `10.0.26-jre11-alpine-eclipse-temurin`, `10.0-jre11-alpine-eclipse-temurin`, `10-jre11-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jre11-alpine/Dockerfile)
-
 -	[`10.0.26-jre11`, `10.0-jre11`, `10-jre11`, `10.0.26-jre11-eclipse-temurin`, `10.0-jre11-eclipse-temurin`, `10-jre11-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jre11/Dockerfile)
 
--	[`10.0.26-jdk21-alpine`, `10.0-jdk21-alpine`, `10-jdk21-alpine`, `10.0.26-jdk21-alpine-eclipse-temurin`, `10.0-jdk21-alpine-eclipse-temurin`, `10-jdk21-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jdk21-alpine/Dockerfile)
-
 -	[`10.0.26`, `10.0`, `10`, `10.0.26-jdk21`, `10.0-jdk21`, `10-jdk21`, `10.0.26-eclipse-temurin`, `10.0-eclipse-temurin`, `10-eclipse-temurin`, `10.0.26-jdk21-eclipse-temurin`, `10.0-jdk21-eclipse-temurin`, `10-jdk21-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jdk21/Dockerfile)
 
--	[`10.0.26-jdk17-alpine`, `10.0-jdk17-alpine`, `10-jdk17-alpine`, `10.0.26-jdk17-alpine-eclipse-temurin`, `10.0-jdk17-alpine-eclipse-temurin`, `10-jdk17-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jdk17-alpine/Dockerfile)
-
 -	[`10.0.26-jdk17`, `10.0-jdk17`, `10-jdk17`, `10.0.26-jdk17-eclipse-temurin`, `10.0-jdk17-eclipse-temurin`, `10-jdk17-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jdk17/Dockerfile)
 
--	[`10.0.26-jdk11-alpine`, `10.0-jdk11-alpine`, `10-jdk11-alpine`, `10.0.26-jdk11-alpine-eclipse-temurin`, `10.0-jdk11-alpine-eclipse-temurin`, `10-jdk11-alpine-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jdk11-alpine/Dockerfile)
-
 -	[`10.0.26-jdk11`, `10.0-jdk11`, `10-jdk11`, `10.0.26-jdk11-eclipse-temurin`, `10.0-jdk11-eclipse-temurin`, `10-jdk11-eclipse-temurin`](https://github.com/eclipse/jetty.docker/blob/5a8d565c6959453cf11c2906059be01adc848004/eclipse-temurin/10.0/jdk11/Dockerfile)
 
 -	[`9.4.58-jdk8-alpine-amazoncorretto`, `9.4-jdk8-alpine-amazoncorretto`, `9-jdk8-alpine-amazoncorretto`](https://github.com/eclipse/jetty.docker/blob/eb7150579b055f3094f50e70f67678b9209baaf7/amazoncorretto/9.4/jdk8-alpine/Dockerfile)
@@ -224,13 +174,13 @@ Jetty is a pure Java-based HTTP (Web) server and Java Servlet container. While W
 To run the default Jetty server in the background, use the following command:
 
 ```console
-$ docker run -d jetty
+$ docker run -d arm64v8/jetty
 ```
 
 You can test it by visiting `http://container-ip:8080` or `https://container-ip:8443/` in a browser. To expose your Jetty server to outside requests, use a port mapping as follows:
 
 ```console
-$ docker run -d -p 80:8080 -p 443:8443 jetty
+$ docker run -d -p 80:8080 -p 443:8443 arm64v8/jetty
 ```
 
 This will map port 8080 inside the container as port 80 on the host and container port 8443 as host port 443. You can then go to `http://host-ip` or `https://host-ip` in a browser.
@@ -254,19 +204,19 @@ For older EOL'd images based on Jetty 7 or Jetty 8, please follow the [legacy in
 The configuration of the Jetty server can be reported by running with the `--list-config` option:
 
 ```console
-$ docker run -d jetty --list-config
+$ docker run -d arm64v8/jetty --list-config
 ```
 
 Configuration such as parameters and additional modules may also be passed in via the command line. For example:
 
 ```console
-$ docker run -d jetty --module=jmx jetty.threadPool.maxThreads=500
+$ docker run -d arm64v8/jetty --module=jmx jetty.threadPool.maxThreads=500
 ```
 
 To update the server configuration in a derived Docker image, the `Dockerfile` may enable additional modules with `RUN` commands like:
 
 ```Dockerfile
-FROM jetty
+FROM arm64v8/jetty
 
 RUN java -jar "$JETTY_HOME/start.jar" --add-to-startd=jmx,stats
 ```
@@ -278,15 +228,15 @@ Modules may be configured in a `Dockerfile` by editing the properties in the cor
 JVM options can be set by passing the `JAVA_OPTIONS` environment variable to the container. For example, to set the maximum heap size to 1 gigabyte, you can run the container as follows:
 
 ```console
-$ docker run -e JAVA_OPTIONS="-Xmx1g" -d jetty
+$ docker run -e JAVA_OPTIONS="-Xmx1g" -d arm64v8/jetty
 ```
 
 ## Read-only container
 
-To run `jetty` as a read-only container, have Docker create the `/tmp/jetty` and `/run/jetty` directories as volumes:
+To run `arm64v8/jetty` as a read-only container, have Docker create the `/tmp/jetty` and `/run/jetty` directories as volumes:
 
 ```console
-$ docker run -d --read-only -v /tmp/jetty -v /run/jetty jetty
+$ docker run -d --read-only -v /tmp/jetty -v /run/jetty arm64v8/jetty
 ```
 
 Since the container is read-only, you'll need to either mount in your webapps directory with `-v /path/to/my/webapps:/var/lib/jetty/webapps` or by populating `/var/lib/jetty/webapps` in a derived image.
@@ -296,7 +246,7 @@ Since the container is read-only, you'll need to either mount in your webapps di
 Starting with version 9.3, Jetty comes with built-in support for HTTP/2. However, due to potential license compatiblity issues with the ALPN library used to implement HTTP/2, the module is not enabled by default. In order to enable HTTP/2 support in a derived `Dockerfile` for private use, you can add a `RUN` command that enables the `http2` module and approve its license as follows:
 
 ```Dockerfile
-FROM jetty
+FROM arm64v8/jetty
 
 RUN java -jar $JETTY_HOME/start.jar --add-to-startd=http2 --approve-all-licenses
 ```
@@ -310,18 +260,18 @@ By default, this image starts as user `root` and uses Jetty's `setuid` module to
 If you would like the image to start immediately as user `jetty` instead of starting as `root`, you can start the container with `-u jetty`:
 
 ```console
-$ docker run -d -u jetty jetty
+$ docker run -d -u jetty arm64v8/jetty
 ```
 
 # Image Variants
 
-The `jetty` images come in many flavors, each designed for a specific use case.
+The `arm64v8/jetty` images come in many flavors, each designed for a specific use case.
 
-## `jetty:<version>`
+## `arm64v8/jetty:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `jetty:<version>-alpine`
+## `arm64v8/jetty:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

joomla/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `joomla` official image](https://hub.docker.com/_/joomla) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -72,7 +74,7 @@ Joomla is a free and open-source content management system (CMS) for publishing
 # How to use this image
 
 ```console
-$ docker run --name some-joomla --network some-network -d joomla
+$ docker run --name some-joomla --network some-network -d arm64v8/joomla
 ```
 
 The following environment variables are honored for configuring your Joomla instance:
@@ -101,7 +103,7 @@ The following environment variables are also honored for configuring auto deploy
 If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:
 
 ```console
-$ docker run --name some-joomla --network some-network -p 8080:80 -d joomla
+$ docker run --name some-joomla --network some-network -p 8080:80 -d arm64v8/joomla
 ```
 
 Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browser.
@@ -110,7 +112,7 @@ If you'd like to use an external database instead of a MySQL container, specify
 
 ```console
 $ docker run --name some-joomla --network some-network -e JOOMLA_DB_HOST=10.1.2.3:3306 \
-    -e JOOMLA_DB_USER=... -e JOOMLA_DB_PASSWORD=... -d joomla
+    -e JOOMLA_DB_USER=... -e JOOMLA_DB_PASSWORD=... -d arm64v8/joomla
 ```
 
 ## ... via [`docker compose`](https://github.com/docker/compose)
@@ -175,13 +177,13 @@ The following Docker Hub features can help with the task of keeping your depende
 
 # Image Variants
 
-The `joomla` images come in many flavors, each designed for a specific use case.
+The `arm64v8/joomla` images come in many flavors, each designed for a specific use case.
 
-## `joomla:<version>`
+## `arm64v8/joomla:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `joomla:<version>-alpine`
+## `arm64v8/joomla:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

jruby/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `jruby` official image](https://hub.docker.com/_/jruby) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -132,7 +134,7 @@ JRuby leverages the robustness and speed of the JVM while providing the same Rub
 ## Create a `Dockerfile` in your Ruby app project
 
 ```dockerfile
-FROM jruby:10
+FROM arm64v8/jruby:10
 
 # throw errors if Gemfile has been modified since Gemfile.lock
 RUN bundle config --global frozen 1
@@ -161,7 +163,7 @@ $ docker run -it --name my-running-script my-ruby-app
 The above example `Dockerfile` expects a `Gemfile.lock` in your app directory. This `docker run` will help you generate one. Run it in the root of your app, next to the `Gemfile`:
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/app -w /usr/src/app jruby:10 bundle install --system
+$ docker run --rm -v "$PWD":/usr/src/app -w /usr/src/app arm64v8/jruby:10 bundle install --system
 ```
 
 ## Run a single Ruby script
@@ -169,7 +171,7 @@ $ docker run --rm -v "$PWD":/usr/src/app -w /usr/src/app jruby:10 bundle install
 For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Ruby script by using the Ruby Docker image directly:
 
 ```console
-$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp jruby:10 jruby your-daemon-or-script.rb
+$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/jruby:10 jruby your-daemon-or-script.rb
 ```
 
 # License

julia/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `julia` official image](https://hub.docker.com/_/julia) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -32,64 +34,27 @@ WARNING:
 
 -	[`1.12.0-bookworm`, `1.12-bookworm`, `1-bookworm`, `bookworm`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/bookworm/Dockerfile)
 
--	[`1.12.0-windowsservercore-ltsc2025`, `1.12-windowsservercore-ltsc2025`, `1-windowsservercore-ltsc2025`, `windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`1.12.0-windowsservercore-ltsc2022`, `1.12-windowsservercore-ltsc2022`, `1-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/windows/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`1.11.7-trixie`, `1.11-trixie`](https://github.com/docker-library/julia/blob/fa7463443f367283c168038f5fe7d5f40a960b66/1.11/trixie/Dockerfile)
 
 -	[`1.11.7-bookworm`, `1.11-bookworm`](https://github.com/docker-library/julia/blob/fa7463443f367283c168038f5fe7d5f40a960b66/1.11/bookworm/Dockerfile)
 
--	[`1.11.7-windowsservercore-ltsc2025`, `1.11-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/b490d5cf6af9a5f1d001d1a093c4313e8fbe3333/1.11/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`1.11.7-windowsservercore-ltsc2022`, `1.11-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/b490d5cf6af9a5f1d001d1a093c4313e8fbe3333/1.11/windows/windowsservercore-ltsc2022/Dockerfile)
-
 -	[`1.10.10-trixie`, `1.10-trixie`](https://github.com/docker-library/julia/blob/25081b47fd632d8a7140a3fede2da1db2d96aee5/1.10/trixie/Dockerfile)
 
 -	[`1.10.10-bookworm`, `1.10-bookworm`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/bookworm/Dockerfile)
 
--	[`1.10.10-alpine3.22`, `1.10-alpine3.22`, `1.10.10-alpine`, `1.10-alpine`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/alpine3.22/Dockerfile)
-
--	[`1.10.10-alpine3.21`, `1.10-alpine3.21`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/alpine3.21/Dockerfile)
-
--	[`1.10.10-windowsservercore-ltsc2025`, `1.10-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`1.10.10-windowsservercore-ltsc2022`, `1.10-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/windows/windowsservercore-ltsc2022/Dockerfile)
-
 ## Shared Tags
 
 -	`1.12.0`, `1.12`, `1`, `latest`:
 
 	-	[`1.12.0-trixie`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/trixie/Dockerfile)
-	-	[`1.12.0-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.12.0-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.12.0-windowsservercore`, `1.12-windowsservercore`, `1-windowsservercore`, `windowsservercore`:
-
-	-	[`1.12.0-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.12.0-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/30e953f8abfa024651984120929c403b7cdf5a9a/1.12/windows/windowsservercore-ltsc2022/Dockerfile)
 
 -	`1.11.7`, `1.11`:
 
 	-	[`1.11.7-trixie`](https://github.com/docker-library/julia/blob/fa7463443f367283c168038f5fe7d5f40a960b66/1.11/trixie/Dockerfile)
-	-	[`1.11.7-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/b490d5cf6af9a5f1d001d1a093c4313e8fbe3333/1.11/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.11.7-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/b490d5cf6af9a5f1d001d1a093c4313e8fbe3333/1.11/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.11.7-windowsservercore`, `1.11-windowsservercore`:
-
-	-	[`1.11.7-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/b490d5cf6af9a5f1d001d1a093c4313e8fbe3333/1.11/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.11.7-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/b490d5cf6af9a5f1d001d1a093c4313e8fbe3333/1.11/windows/windowsservercore-ltsc2022/Dockerfile)
 
 -	`1.10.10`, `1.10`:
 
 	-	[`1.10.10-trixie`](https://github.com/docker-library/julia/blob/25081b47fd632d8a7140a3fede2da1db2d96aee5/1.10/trixie/Dockerfile)
-	-	[`1.10.10-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.10.10-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`1.10.10-windowsservercore`, `1.10-windowsservercore`:
-
-	-	[`1.10.10-windowsservercore-ltsc2025`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`1.10.10-windowsservercore-ltsc2022`](https://github.com/docker-library/julia/blob/36ec8a84fe6a3ac59872725f20e892e472b45227/1.10/windows/windowsservercore-ltsc2022/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -131,41 +96,15 @@ It's especially relevant to note that Alpine / musl is "Tier 3" due to several k
 Starting the Julia REPL is as easy as the following:
 
 ```console
-$ docker run -it --rm julia
+$ docker run -it --rm arm64v8/julia
 ```
 
 ## Run Julia script from your local directory inside container
 
 ```console
-$ docker run -it --rm -v "$PWD":/usr/myapp -w /usr/myapp julia julia script.jl arg1 arg2
+$ docker run -it --rm -v "$PWD":/usr/myapp -w /usr/myapp arm64v8/julia julia script.jl arg1 arg2
 ```
 
-# Image Variants
-
-The `julia` images come in many flavors, each designed for a specific use case.
-
-## `julia:<version>`
-
-This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
-
-Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
-
-## `julia:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
-## `julia:<version>-alpine`
-
-This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
-
-This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use [musl libc](https://musl.libc.org) instead of [glibc and friends](https://www.etalabs.net/compare_libcs.html), so software will often run into issues depending on the depth of their libc requirements/assumptions. See [this Hacker News comment thread](https://news.ycombinator.com/item?id=10782897) for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
-
-To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
-
 # License
 
 View [license information](http://julialang.org/) for the software contained in this image.

kapacitor/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `kapacitor` official image](https://hub.docker.com/_/kapacitor) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -26,12 +28,8 @@ WARNING:
 
 -	[`1.7`, `1.7.7`](https://github.com/influxdata/influxdata-docker/blob/add887456e0d1657ae822e422bc5cbb2b9b723bc/kapacitor/1.7/Dockerfile)
 
--	[`1.7-alpine`, `1.7.7-alpine`, `alpine`](https://github.com/influxdata/influxdata-docker/blob/add887456e0d1657ae822e422bc5cbb2b9b723bc/kapacitor/1.7/alpine/Dockerfile)
-
 -	[`1.8`, `1.8.2`, `latest`](https://github.com/influxdata/influxdata-docker/blob/add887456e0d1657ae822e422bc5cbb2b9b723bc/kapacitor/1.8/Dockerfile)
 
--	[`1.8-alpine`, `1.8.2-alpine`](https://github.com/influxdata/influxdata-docker/blob/add887456e0d1657ae822e422bc5cbb2b9b723bc/kapacitor/1.8/alpine/Dockerfile)
-
 # Quick reference (cont.)
 
 -	**Where to file issues**:  
@@ -66,7 +64,7 @@ Kapacitor is an open source data processing engine written in Go. It can process
 Start the Kapacitor container with default options:
 
 ```console
-$ docker run -p 9092:9092 kapacitor
+$ docker run -p 9092:9092 arm64v8/kapacitor
 ```
 
 Start the Kapacitor container sharing the data directory with the host:
@@ -74,7 +72,7 @@ Start the Kapacitor container sharing the data directory with the host:
 ```console
 $ docker run -p 9092:9092 \
       -v $PWD:/var/lib/kapacitor \
-      kapacitor
+      arm64v8/kapacitor
 ```
 
 Modify `$PWD` to the directory where you want to store data associated with the Kapacitor container.
@@ -84,7 +82,7 @@ You can also have Docker control the volume mountpoint by using a named volume.
 ```console
 $ docker run -p 9092:9092 \
       -v kapacitor:/var/lib/kapacitor \
-      kapacitor
+      arm64v8/kapacitor
 ```
 
 ### Configuration
@@ -94,7 +92,7 @@ Kapacitor can be either configured from a config file or using environment varia
 Generate the default configuration file:
 
 ```console
-$ docker run --rm kapacitor kapacitord config > kapacitor.conf
+$ docker run --rm arm64v8/kapacitor kapacitord config > kapacitor.conf
 ```
 
 Modify the default configuration, which will now be available under `$PWD`. Then start the Kapacitor container.
@@ -102,7 +100,7 @@ Modify the default configuration, which will now be available under `$PWD`. Then
 ```console
 $ docker run -p 9092:9092 \
       -v $PWD/kapacitor.conf:/etc/kapacitor/kapacitor.conf:ro \
-      kapacitor
+      arm64v8/kapacitor
 ```
 
 Modify `$PWD` to the directory where you want to store the configuration file.
@@ -154,7 +152,7 @@ $ docker run -p 9092:9092 \
     -h kapacitor \
     --net=influxdb \
     -e KAPACITOR_INFLUXDB_0_URLS_0=http://influxdb:8086 \
-    kapacitor
+    arm64v8/kapacitor
 ```
 
 You can also start Kapacitor sharing the same network interface of the InfluxDB container. If you do this, Docker will act as if both processes were being run on the same machine.
@@ -163,7 +161,7 @@ You can also start Kapacitor sharing the same network interface of the InfluxDB
 $ docker run -p 9092:9092 \
       --name=kapacitor \
       --net=container:influxdb \
-      kapacitor
+      arm64v8/kapacitor
 ```
 
 When run like this, InfluxDB can be communicated with over `localhost`.
@@ -173,7 +171,7 @@ When run like this, InfluxDB can be communicated with over `localhost`.
 Start the container:
 
 ```console
-$ docker run --name=kapacitor -d -p 9092:9092 kapacitor
+$ docker run --name=kapacitor -d -p 9092:9092 arm64v8/kapacitor
 ```
 
 Run another container linked to the `kapacitor` container for using the client. Set the env `KAPACITOR_URL` so the client knows how to connect to Kapacitor. Mount in your current directory for accessing TICKscript files.
@@ -181,29 +179,13 @@ Run another container linked to the `kapacitor` container for using the client.
 ```console
 $ docker run --rm --net=container:kapacitor \
       -v $PWD:/root -w=/root -it \
-      kapacitor bash -l
+      arm64v8/kapacitor bash -l
 ```
 
 Then, from within the container, you can use the `kapacitor` command to interact with the daemon.
 
 See [this](https://docs.influxdata.com/kapacitor/latest/introduction/getting_started/) for a more detailed getting started guide with Kapacitor.
 
-# Image Variants
-
-The `kapacitor` images come in many flavors, each designed for a specific use case.
-
-## `kapacitor:<version>`
-
-This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
-
-## `kapacitor:<version>-alpine`
-
-This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
-
-This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use [musl libc](https://musl.libc.org) instead of [glibc and friends](https://www.etalabs.net/compare_libcs.html), so software will often run into issues depending on the depth of their libc requirements/assumptions. See [this Hacker News comment thread](https://news.ycombinator.com/item?id=10782897) for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
-
-To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
-
 # License
 
 View [license information](https://github.com/influxdata/kapacitor/blob/master/LICENSE) for the software contained in this image.

kibana/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `kibana` official image](https://hub.docker.com/_/kibana) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

kong/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `kong` official image](https://hub.docker.com/_/kong) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -30,8 +32,6 @@ WARNING:
 
 -	[`3.4.2-ubuntu`, `3.4-ubuntu`, `3.4.2`, `3.4`](https://github.com/Kong/docker-kong/blob/e07de903edf213445a0540172d51529ac344b448/ubuntu/Dockerfile)
 
--	[`2.8.5-ubuntu`, `2.8-ubuntu`](https://github.com/Kong/docker-kong/blob/cdf93ae2106f998a2245a3eee6814b1ae68781af/ubuntu/Dockerfile)
-
 # Quick reference (cont.)
 
 -	**Where to file issues**:  

krakend/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `krakend` official image](https://hub.docker.com/_/krakend) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -68,7 +70,7 @@ To use the image, `COPY` your `krakend.json` file inside the container or mount
 You can start an empty gateway with a health check with the following commands:
 
 ```bash
-docker run -d -p 8080:8080 -v "$PWD:/etc/krakend/" krakend
+docker run -d -p 8080:8080 -v "$PWD:/etc/krakend/" arm64v8/krakend
 
 curl http://localhost:8080/__health
 {"agents":{},"now":"2024-05-23 14:35:55.552591448 +0000 UTC m=+26.856583003","status":"ok"}
@@ -85,7 +87,7 @@ The configuration files are taken from the current directory (`$PWD`). Therefore
 This flag is **SAFE to use in production**. It's meant to enable KrakenD as a fake backend itself by enabling a [`/__debug` endpoint](https://www.krakend.io/docs/endpoints/debug-endpoint/)
 
 ```bash
-docker run -p 8080:8080 -v "${PWD}:/etc/krakend/" krakend run -d -c /etc/krakend/krakend.json
+docker run -p 8080:8080 -v "${PWD}:/etc/krakend/" arm64v8/krakend run -d -c /etc/krakend/krakend.json
 ```
 
 #### Checking the syntax of your configuration file
@@ -93,23 +95,23 @@ docker run -p 8080:8080 -v "${PWD}:/etc/krakend/" krakend run -d -c /etc/krakend
 See the [check command](https://www.krakend.io/docs/commands/check/)
 
 ```bash
-docker run -it -v $PWD:/etc/krakend/ krakend check --config krakend.json
+docker run -it -v $PWD:/etc/krakend/ arm64v8/krakend check --config krakend.json
 ```
 
 #### Show the help:
 
 ```bash
-docker run --rm -it krakend help
+docker run --rm -it arm64v8/krakend help
 ```
 
 ### Building your custom KrakenD image
 
-Most production deployments will not want to rely on mounting a volume for the container but to use their image based on `krakend`:
+Most production deployments will not want to rely on mounting a volume for the container but to use their image based on `arm64v8/krakend`:
 
 Your `Dockerfile` could look like this:
 
 ```Dockerfile
-FROM krakend:<version>
+FROM arm64v8/krakend:<version>
 # NOTE: Avoid using :latest image on production. Stick to a major version instead.
 
 COPY krakend.json ./
@@ -121,7 +123,7 @@ RUN krakend check -t --lint-no-network -c krakend.json
 If you want to manage your KrakenD configuration using multiple files and folders, reusing templates, and distributing the configuration amongst your teams, you can use the [flexible configuration (FC)](https://www.krakend.io/docs/configuration/flexible-config/). The following `Dockerfile` combines FC, the `krakend check` command, and a 2-step build.
 
 ```Dockerfile
-FROM krakend:<version> as builder
+FROM arm64v8/krakend:<version> as builder
 
 COPY krakend.tmpl .
 COPY config .
@@ -135,7 +137,7 @@ RUN FC_ENABLE=1 \
     krakend check -d -t -c krakend.tmpl
 
 # Copy the output file only and discard any other files
-FROM krakend:<version>
+FROM arm64v8/krakend:<version>
 COPY --from=builder /tmp/krakend.json .
 ```
 
@@ -160,7 +162,7 @@ Finally, a simple `docker compose` file to start KrakenD with your API would be:
 ```yaml
 services:
   krakend:
-    image: krakend:<version>
+    image: arm64v8/krakend:<version>
     ports:
       - "8080:8080"
     volumes:
@@ -172,7 +174,7 @@ And another one that uses the flexible configuration and a custom template filen
 ```yaml
 services:
   krakend:
-    image: krakend:<version>
+    image: arm64v8/krakend:<version>
     ports:
       - "8080:8080"
     volumes:
@@ -194,8 +196,8 @@ All `krakend` commands are executed as `krakend` user (uid=1000), and the rest o
 You can directly use sub-commands of `krakend` like `run`, `help`, `version`, `check`, `check-plugin`, or `test-plugin` as the entrypoint will add the `krakend` command automatically. For example, the following lines are equivalent:
 
 ```bash
-docker run --rm -it krakend help
-docker run --rm -it krakend krakend help
+docker run --rm -it arm64v8/krakend help
+docker run --rm -it arm64v8/krakend krakend help
 ```
 
 # License

lightstreamer/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `lightstreamer` official image](https://hub.docker.com/_/lightstreamer) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -88,7 +90,7 @@ For more information and related downloads for Lightstreamer Server and other Li
 Launch the container with the default configuration:
 
 ```console
-$ docker run --name ls-server -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 This will map port 8080 inside the container to port 80 on local host. Then point your browser to `http://localhost` and watch the Welcome page showing real-time data flowing in from the locally deployed demo application, which is a first overview of the unique features offered by the Lightstreamer technology. More examples are available online at the [demo site](https://demos.lightstreamer.com).
@@ -98,25 +100,25 @@ This will map port 8080 inside the container to port 80 on local host. Then poin
 It is possible to customize each aspect of the Lightstreamer instance running into the container. For example, a specific configuration file may be supplied as follows:
 
 ```console
-$ docker run --name ls-server -v /path/to/my-lightstreamer_conf.xml:/lightstreamer/conf/lightstreamer_conf.xml -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/my-lightstreamer_conf.xml:/lightstreamer/conf/lightstreamer_conf.xml -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 In the same way, you could provide a custom logging configuration, maybe in this case also specifying a dedicated volume to ensure both the persistence of log files and better performance of the container:
 
 ```console
-$ docker run --name ls-server -v /path/to/my-lightstreamer_log_conf.xml:/lightstreamer/conf/lightstreamer_log_conf.xml -v /path/to/logs:/lightstreamer/logs -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/my-lightstreamer_log_conf.xml:/lightstreamer/conf/lightstreamer_log_conf.xml -v /path/to/logs:/lightstreamer/logs -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 If you also change in your `my-lightstreamer_log_conf.xml` file the default logging path from `../logs` to `/path/to/dest/logs`:
 
 ```console
-$ docker run --name ls-server -v /path/to/my-lightstreamer_log_conf.xml:/lightstreamer/conf/lightstreamer_log_conf.xml -v /path/to/hosted/logs:/path/to/dest/logs -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/my-lightstreamer_log_conf.xml:/lightstreamer/conf/lightstreamer_log_conf.xml -v /path/to/hosted/logs:/path/to/dest/logs -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 Alternatively, the above tasks can be executed by deriving a new image through a `Dockerfile` as the following:
 
 ```dockerfile
-FROM lightstreamer
+FROM arm64v8/lightstreamer
 
 # Please specify a COPY command only for the required custom configuration file
 COPY my-lightstreamer_conf.xml /lightstreamer/conf/lightstreamer_conf.xml
@@ -148,7 +150,7 @@ To accomplish such goal, you may use similar strategies to those illustrated abo
 To deploy a single custom Adapter Set, the simplest way is to attach its files into the factory adapters folder, as follows:
 
 ```console
-$ docker run --name ls-server -v /path/to/my-adapter-set:/lightstreamer/adapters/my-adapter-set -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/my-adapter-set:/lightstreamer/adapters/my-adapter-set -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 ### Full replacement of the "adapters" folder
@@ -156,7 +158,7 @@ $ docker run --name ls-server -v /path/to/my-adapter-set:/lightstreamer/adapters
 In the case you have many custom Adapter Sets to deploy, a more appropriate strategy is to replace the factory adapters folder with the one located in your host machine:
 
 ```console
-$ docker run --name ls-server -v /path/to/my-adapters:/lightstreamer/adapters -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/my-adapters:/lightstreamer/adapters -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 In this case, the `/path/to/my-adapters` folder has to be structured with the required layout for an adapters folder:
@@ -176,7 +178,7 @@ Once again, a linear and clean approach is to make a new image including all nee
 In this case, you could write a simple Docker file in which the list of all your Adapter Sets configuration files is provided:
 
 ```dockerfile
-FROM lightstreamer
+FROM arm64v8/lightstreamer
 
 # Will copy the contents of N Adapter Sets into the factory adapters folder
 COPY my-adapter-set-1 /lightstreamer/adapters/my-adapter-set-1
@@ -193,7 +195,7 @@ There might be some circumstances where you would like to provide custom pages f
 For example, with the following command you will be able to fully replace the factory `pages` folder:
 
 ```console
-$ docker run --name ls-server -v /path/to/custom/pages:/lightstreamer/pages -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/custom/pages:/lightstreamer/pages -d -p 80:8080 arm64v8/lightstreamer
 ```
 
 where `/path/to/custom/pages` is the path in your host machine containing the replacing web content files.

liquibase/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `liquibase` official image](https://hub.docker.com/_/liquibase) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -66,20 +68,20 @@ $ liquibase update --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATA
 The only change to use this docker image, is to use `docker run ...` and mount the folder containing your changelog.xml (or .yml or .json or .sql) to `/liquibase/changelog` in the Liquibase container
 
 ```console
-$ docker run -v /home/user/changelog:/liquibase/changelog liquibase --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATABASE_IP>:<DATABASE_PORT>/<DATABASE>" --changeLogFile=/liquibase/changelog/changelog.xml --username=<USERNAME> --password=<PASSWORD>
+$ docker run -v /home/user/changelog:/liquibase/changelog arm64v8/liquibase --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATABASE_IP>:<DATABASE_PORT>/<DATABASE>" --changeLogFile=/liquibase/changelog/changelog.xml --username=<USERNAME> --password=<PASSWORD>
 ```
 
 All Liquibase commands, such as `rollback`, `updateSQL`, and others, are available, as well.
 
 # Image Variants
 
-The `liquibase` images come in many flavors, each designed for a specific use case.
+The `arm64v8/liquibase` images come in many flavors, each designed for a specific use case.
 
-## `liquibase:<version>`
+## `arm64v8/liquibase:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `liquibase:<version>-alpine`
+## `arm64v8/liquibase:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

logstash/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `logstash` official image](https://hub.docker.com/_/logstash) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  

mageia/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `mageia` official image](https://hub.docker.com/_/mageia) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,9 +26,9 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`9`, `latest`](https://github.com/juanluisbaptiste/docker-brew-mageia/blob/56f63e76f2588a3ad69ee13bacedb979bcfc2542/dist/9/x86_64/Dockerfile)
+-	[`9`, `latest`](https://github.com/juanluisbaptiste/docker-brew-mageia/blob/56f63e76f2588a3ad69ee13bacedb979bcfc2542/dist/9/aarch64/Dockerfile)
 
--	[`cauldron`](https://github.com/juanluisbaptiste/docker-brew-mageia/blob/56f63e76f2588a3ad69ee13bacedb979bcfc2542/dist/cauldron/x86_64/Dockerfile)
+-	[`cauldron`](https://github.com/juanluisbaptiste/docker-brew-mageia/blob/56f63e76f2588a3ad69ee13bacedb979bcfc2542/dist/cauldron/aarch64/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -68,7 +70,7 @@ To date, Mageia:
 ## Create a Dockerfile for your container
 
 ```dockerfile
-FROM mageia:6
+FROM arm64v8/mageia:6
 MAINTAINER  "Foo Bar" <[email protected]>
 CMD [ "bash" ]
 ```

mariadb/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `mariadb` official image](https://hub.docker.com/_/mariadb) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -79,7 +81,7 @@ The intent is also to maintain high compatibility with MySQL, ensuring a library
 
 # How to use this image
 
-The mariadb has a number of tags, and of note is `latest`, as the latest stable version, and `lts`, as the last long term support release.
+The arm64v8/mariadb has a number of tags, and of note is `latest`, as the latest stable version, and `lts`, as the last long term support release.
 
 ## Running the container
 
@@ -90,7 +92,7 @@ The mariadb has a number of tags, and of note is `latest`, as the latest stable
 By default, the database running within the container will listen on port 3306. You can expose the container port 3306 to the host port 3306 with the `-p 3306:3306` argument to `docker run`, like the command below:
 
 ```console
-$ docker run --name some-mariadb -p 3306:3306 mariadb:latest
+$ docker run --name some-mariadb -p 3306:3306 arm64v8/mariadb:latest
 ```
 
 ### Starting using a minimal configuration
@@ -98,19 +100,19 @@ $ docker run --name some-mariadb -p 3306:3306 mariadb:latest
 The environment variables required to use this image involves the setting of the root user password:
 
 ```console
-$ docker run --detach --name some-mariadb --env MARIADB_ROOT_PASSWORD=my-secret-pw mariadb:latest
+$ docker run --detach --name some-mariadb --env MARIADB_ROOT_PASSWORD=my-secret-pw arm64v8/mariadb:latest
 ```
 
 or:
 
 ```console
-$ docker run --detach --name some-mariadb --env MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1 mariadb:latest
+$ docker run --detach --name some-mariadb --env MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1 arm64v8/mariadb:latest
 ```
 
 or:
 
 ```console
-$ docker run --detach --name some-mariadb --env MARIADB_RANDOM_ROOT_PASSWORD=1 mariadb:latest
+$ docker run --detach --name some-mariadb --env MARIADB_RANDOM_ROOT_PASSWORD=1 arm64v8/mariadb:latest
 ```
 
 ... where the container logs will contain the generated root password.
@@ -139,21 +141,21 @@ services:
 
 Run `docker compose up`, wait for it to initialize completely, and visit `http://localhost:8080` or `http://host-ip:8080` (as appropriate).
 
-### Start a `mariadb` server instance with user, password and database
+### Start a `arm64v8/mariadb` server instance with user, password and database
 
 Starting a MariaDB instance with a user, password, and a database:
 
 ```console
-$ docker run --detach --name some-mariadb --env MARIADB_USER=example-user --env MARIADB_PASSWORD=my_cool_secret --env MARIADB_DATABASE=exmple-database --env MARIADB_ROOT_PASSWORD=my-secret-pw mariadb:latest
+$ docker run --detach --name some-mariadb --env MARIADB_USER=example-user --env MARIADB_PASSWORD=my_cool_secret --env MARIADB_DATABASE=exmple-database --env MARIADB_ROOT_PASSWORD=my-secret-pw arm64v8/mariadb:latest
 ```
 
-### Start a `mariadb` server instance in a network
+### Start a `arm64v8/mariadb` server instance in a network
 
 As applications talk to MariaDB, MariaDB needs to start in the same network as the application:
 
 ```console
 $ docker network create some-network 
-$ docker run --detach --network some-network --name some-mariadb --env MARIADB_USER=example-user --env MARIADB_PASSWORD=my_cool_secret --env MARIADB_ROOT_PASSWORD=my-secret-pw mariadb:latest
+$ docker run --detach --network some-network --name some-mariadb --env MARIADB_USER=example-user --env MARIADB_PASSWORD=my_cool_secret --env MARIADB_ROOT_PASSWORD=my-secret-pw arm64v8/mariadb:latest
 $ docker run --detach --network some-network --name some-application --env APP_DB_HOST=some-mariadb --env APP_DB_USER=example-user --env APP_DB_PASSWD=my_cool_secret some-application
 ```
 
@@ -161,18 +163,18 @@ $ docker run --detach --network some-network --name some-application --env APP_D
 
 ## Connect to MariaDB from the MariaDB command line client
 
-The following command starts another `mariadb` container instance and runs the `mariadb` command line client against your original `mariadb` container, allowing you to execute SQL statements against your database instance:
+The following command starts another `arm64v8/mariadb` container instance and runs the `mariadb` command line client against your original `arm64v8/mariadb` container, allowing you to execute SQL statements against your database instance:
 
 ```console
-$ docker run -it --network some-network --rm mariadb mariadb -h some-mariadb -u example-user
+$ docker run -it --network some-network --rm arm64v8/mariadb mariadb -h some-mariadb -u example-user
 ```
 
-... where `some-mariadb` is the name of your original `mariadb` container (connected to the `some-network` Docker network).
+... where `some-mariadb` is the name of your original `arm64v8/mariadb` container (connected to the `some-network` Docker network).
 
 This image can also be used as a client for non-Docker or remote instances:
 
 ```console
-$ docker run -it --rm mariadb mariadb --host <server container IP> --user example-user --password --database test
+$ docker run -it --rm arm64v8/mariadb mariadb --host <server container IP> --user example-user --password --database test
 ```
 
 That will give you a standard MariaDB prompt. You can test it with:
@@ -210,7 +212,7 @@ More information about the MariaDB command-line client can be found in the [Mari
 
 ## Container shell access
 
-The `docker exec` command allows you to run commands inside the running container. The following command line will give you a bash shell inside your `mariadb` container:
+The `docker exec` command allows you to run commands inside the running container. The following command line will give you a bash shell inside your `arm64v8/mariadb` container:
 
 ```console
 $ docker exec -it some-mariadb bash
@@ -236,17 +238,17 @@ $ docker logs some-mariadb
 
 Custom configuration files should end in `.cnf` and be mounted read only at the directory `/etc/mysql/conf.d`. These files should contain the minimal changes from the MariaDB workload required for your application/environment. A MariaDB configuration file will have a `[mariadb]` group followed by `variable` = `value` settings per [Setting Server System Variables](https://mariadb.com/kb/en/server-system-variables/#setting-server-system-variables) or [option-prefix-variable](https://mariadb.com/kb/en/configuring-mariadb-with-option-files/#option-prefixes).
 
-The `mariadb` image configuration contains the Ubuntu MariaDB variables with two custom changes for the container:
+The `arm64v8/mariadb` image configuration contains the Ubuntu MariaDB variables with two custom changes for the container:
 
 -	[`host-cache-size=0`](https://mariadb.com/kb/en/server-system-variables/#host_cache_size)
 -	[`skip-name-resolve`](https://mariadb.com/kb/en/server-system-variables/#skip_name_resolve)
 
-These disable the authentication of `user@hostname` users. To re-enable the `skip-name-resolve` use `disable-skip-name-resolve` as variable or argument. When enabled, the `host-cache-size` should be sufficient for the number of containers connecting to the `mariadb`.
+These disable the authentication of `user@hostname` users. To re-enable the `skip-name-resolve` use `disable-skip-name-resolve` as variable or argument. When enabled, the `host-cache-size` should be sufficient for the number of containers connecting to the `arm64v8/mariadb`.
 
-To view the resulting configuration of your `mariadb` container:
+To view the resulting configuration of your `arm64v8/mariadb` container:
 
 ```console
-$ docker run --name some-mariadb -v /my/custom:/etc/mysql/conf.d --rm mariadb:latest my_print_defaults --mysqld
+$ docker run --name some-mariadb -v /my/custom:/etc/mysql/conf.d --rm arm64v8/mariadb:latest my_print_defaults --mysqld
 ```
 
 ### Configuration without a `cnf` file
@@ -254,18 +256,18 @@ $ docker run --name some-mariadb -v /my/custom:/etc/mysql/conf.d --rm mariadb:la
 Many configuration options can be passed as flags to `mariadbd`. This will give you the flexibility to customize the container without needing a `cnf` file. For example, if you want to run on port 3808 just run the following:
 
 ```console
-$ docker run --name some-mariadb -e MARIADB_ROOT_PASSWORD=my-secret-pw -d mariadb:latest --port 3808
+$ docker run --name some-mariadb -e MARIADB_ROOT_PASSWORD=my-secret-pw -d arm64v8/mariadb:latest --port 3808
 ```
 
 If you would like to see a complete list of available options, just run:
 
 ```console
-$ docker run -it --rm mariadb:latest --verbose --help
+$ docker run -it --rm arm64v8/mariadb:latest --verbose --help
 ```
 
 ## Environment Variables
 
-When you start the `mariadb` image, you can adjust the initialization of the MariaDB instance by passing one or more environment variables on the `docker run` command line. Do note that all of the variables, except `MARIADB_AUTO_UPGRADE`, will have no effect if you start the container with a data directory that already contains a database. I.e. any pre-existing database will always be left untouched on container startup.
+When you start the `arm64v8/mariadb` image, you can adjust the initialization of the MariaDB instance by passing one or more environment variables on the `docker run` command line. Do note that all of the variables, except `MARIADB_AUTO_UPGRADE`, will have no effect if you start the container with a data directory that already contains a database. I.e. any pre-existing database will always be left untouched on container startup.
 
 One of `MARIADB_RANDOM_ROOT_PASSWORD`, `MARIADB_ROOT_PASSWORD_HASH`, `MARIADB_ROOT_PASSWORD` or `MARIADB_ALLOW_EMPTY_ROOT_PASSWORD` (or equivalents, including `*_FILE`), is required. The other environment variables are optional.
 
@@ -280,18 +282,18 @@ When this environment variable is set, this will run the [mariadb-upgrade](https
 As an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in `/run/secrets/<secret_name>` files. For example:
 
 ```console
-$ docker run --name some-mysql -e MARIADB_ROOT_PASSWORD_FILE=/run/secrets/mariadb-root -d mariadb:latest
+$ docker run --name some-mysql -e MARIADB_ROOT_PASSWORD_FILE=/run/secrets/mariadb-root -d arm64v8/mariadb:latest
 ```
 
 # Initializing the database contents
 
-When a container is started for the first time, a new database with the specified name will be created and initialized with the provided configuration variables. Furthermore, it will execute files with extensions `.sh`, `.sql`, `.sql.gz`, `.sql.xz` and `.sql.zst` that are found in `/docker-entrypoint-initdb.d`. Files will be executed in alphabetical order. `.sh` files without file execute permission are sourced rather than executed. You can easily populate your `mariadb` services by [mounting a SQL dump into that directory](https://docs.docker.com/storage/bind-mounts/) and provide [custom images](https://docs.docker.com/reference/dockerfile/) with contributed data. SQL files will be imported by default to the database specified by the `MARIADB_DATABASE` variable.
+When a container is started for the first time, a new database with the specified name will be created and initialized with the provided configuration variables. Furthermore, it will execute files with extensions `.sh`, `.sql`, `.sql.gz`, `.sql.xz` and `.sql.zst` that are found in `/docker-entrypoint-initdb.d`. Files will be executed in alphabetical order. `.sh` files without file execute permission are sourced rather than executed. You can easily populate your `arm64v8/mariadb` services by [mounting a SQL dump into that directory](https://docs.docker.com/storage/bind-mounts/) and provide [custom images](https://docs.docker.com/reference/dockerfile/) with contributed data. SQL files will be imported by default to the database specified by the `MARIADB_DATABASE` variable.
 
 # Caveats
 
 ## Where to Store Data
 
-Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `mariadb` images to familiarize themselves with the options available, including:
+Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `arm64v8/mariadb` images to familiarize themselves with the options available, including:
 
 -	Use a named volume using the container manager to manage the storage of your database data [by writing the database files to disk on the host system using its own internal volume management](https://docs.docker.com/storage/volumes/). This is the default and is easy and fairly transparent to the user. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers.
 -	Create a data directory on the host system (outside the container) and [mount this to a directory visible from inside the container](https://docs.docker.com/storage/bind-mounts/). This places the database files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly.
@@ -299,10 +301,10 @@ Important note: There are several ways to store data used by applications that r
 The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:
 
 1.	Create a data directory on a suitable volume on your host system, e.g. `/my/own/datadir`.
-2.	Start your `mariadb` container like this:
+2.	Start your `arm64v8/mariadb` container like this:
 
 	```console
-	$ docker run --name some-mariadb -v /my/own/datadir:/var/lib/mysql:Z -e MARIADB_ROOT_PASSWORD=my-secret-pw -d mariadb:latest
+	$ docker run --name some-mariadb -v /my/own/datadir:/var/lib/mysql:Z -e MARIADB_ROOT_PASSWORD=my-secret-pw -d arm64v8/mariadb:latest
 	```
 
 The `-v /my/own/datadir:/var/lib/mysql:Z` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/mysql` inside the container, where MariaDB by default will write its data files.
@@ -317,7 +319,7 @@ See [the "Official Images" FAQ](https://github.com/docker-library/faq#healthchec
 
 ## Usage against an existing database
 
-If you start your `mariadb` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables.
+If you start your `arm64v8/mariadb` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables.
 
 ## Backups and Restores
 
@@ -338,7 +340,7 @@ This is documented on [MariaDB Knowledge Base : Adding Plugins to the Docker Off
 
 # Compose File Examples
 
-Example compose files using this `mariadb` are located in https://github.com/MariaDB/mariadb-docker in the `/examples` folder.
+Example compose files using this `arm64v8/mariadb` are located in https://github.com/MariaDB/mariadb-docker in the `/examples` folder.
 
 # License
 

matomo/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `matomo` official image](https://hub.docker.com/_/matomo) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -66,7 +68,7 @@ WARNING:
 You can run the Matomo container and service like so:
 
 ```bash
-docker run -d --link some-mysql:db matomo
+docker run -d --link some-mysql:db arm64v8/matomo
 ```
 
 This assumes you've already launched a suitable MySQL or MariaDB database container.
@@ -76,7 +78,7 @@ This assumes you've already launched a suitable MySQL or MariaDB database contai
 Use a Docker volume to keep persistent data:
 
 ```bash
-docker run -d -p 8080:80 --link some-mysql:db -v matomo:/var/www/html matomo
+docker run -d -p 8080:80 --link some-mysql:db -v matomo:/var/www/html arm64v8/matomo
 ```
 
 ## Matomo Installation
@@ -127,13 +129,13 @@ We'd love to hear your feedback and suggestions in the issue tracker: [[https://
 
 # Image Variants
 
-The `matomo` images come in many flavors, each designed for a specific use case.
+The `arm64v8/matomo` images come in many flavors, each designed for a specific use case.
 
-## `matomo:<version>`
+## `arm64v8/matomo:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `matomo:<version>-alpine`
+## `arm64v8/matomo:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

maven/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `maven` official image](https://hub.docker.com/_/maven) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,14 +26,8 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`3.9.11-eclipse-temurin-11-alpine`, `3.9-eclipse-temurin-11-alpine`, `3-eclipse-temurin-11-alpine`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/eclipse-temurin-11-alpine/Dockerfile)
-
 -	[`3.9.11-eclipse-temurin-11-noble`, `3.9.11-eclipse-temurin-11`, `3.9-eclipse-temurin-11-noble`, `3.9-eclipse-temurin-11`, `3-eclipse-temurin-11-noble`, `3-eclipse-temurin-11`](https://github.com/carlossg/docker-maven/blob/64ef35f1a6ef3538a0c7e846647d33ffa6232390/eclipse-temurin-11-noble/Dockerfile)
 
--	[`3.9.11-eclipse-temurin-17-alpine`, `3.9-eclipse-temurin-17-alpine`, `3-eclipse-temurin-17-alpine`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/eclipse-temurin-17-alpine/Dockerfile)
-
--	[`4.0.0-rc-4-eclipse-temurin-17-alpine`](https://github.com/carlossg/docker-maven/blob/3e68954f87f8b9be35921fdd538c4d769362f3bf/eclipse-temurin-17-alpine-maven-4/Dockerfile)
-
 -	[`3.9.11-eclipse-temurin-17-noble`, `3.9.11-eclipse-temurin-17`, `3.9-eclipse-temurin-17-noble`, `3.9-eclipse-temurin-17`, `3-eclipse-temurin-17-noble`, `3-eclipse-temurin-17`](https://github.com/carlossg/docker-maven/blob/64ef35f1a6ef3538a0c7e846647d33ffa6232390/eclipse-temurin-17-noble/Dockerfile)
 
 -	[`4.0.0-rc-4-eclipse-temurin-17-noble`, `4.0.0-rc-4-eclipse-temurin-17`](https://github.com/carlossg/docker-maven/blob/64ef35f1a6ef3538a0c7e846647d33ffa6232390/eclipse-temurin-17-noble-maven-4/Dockerfile)
@@ -52,12 +48,8 @@ WARNING:
 
 -	[`4.0.0-rc-4-eclipse-temurin-25-noble`, `4.0.0-rc-4`, `4.0.0-rc-4-eclipse-temurin`, `4.0.0-rc-4-eclipse-temurin-25`](https://github.com/carlossg/docker-maven/blob/c774f7740e38fa4e4f4cec7153e4819cd9afd635/eclipse-temurin-25-noble-maven-4/Dockerfile)
 
--	[`3.9.11-eclipse-temurin-8-alpine`, `3.9-eclipse-temurin-8-alpine`, `3-eclipse-temurin-8-alpine`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/eclipse-temurin-8-alpine/Dockerfile)
-
 -	[`3.9.11-eclipse-temurin-8-noble`, `3.9.11-eclipse-temurin-8`, `3.9-eclipse-temurin-8-noble`, `3.9-eclipse-temurin-8`, `3-eclipse-temurin-8-noble`, `3-eclipse-temurin-8`](https://github.com/carlossg/docker-maven/blob/64ef35f1a6ef3538a0c7e846647d33ffa6232390/eclipse-temurin-8-noble/Dockerfile)
 
--	[`3.9.11-ibmjava-8`, `3.9.11-ibmjava`, `3.9-ibmjava-8`, `3.9-ibmjava`, `3-ibmjava-8`, `3-ibmjava`, `ibmjava`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/ibmjava-8/Dockerfile)
-
 -	[`3.9.11-ibm-semeru-11-noble`, `3.9-ibm-semeru-11-noble`, `3-ibm-semeru-11-noble`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/ibm-semeru-11-noble/Dockerfile)
 
 -	[`3.9.11-ibm-semeru-17-noble`, `3.9-ibm-semeru-17-noble`, `3-ibm-semeru-17-noble`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/ibm-semeru-17-noble/Dockerfile)
@@ -144,8 +136,6 @@ WARNING:
 
 -	[`3.9.11-amazoncorretto-8-debian`, `3.9.11-amazoncorretto-8-debian-trixie`, `3.9-amazoncorretto-8-debian`, `3.9-amazoncorretto-8-debian-trixie`, `3-amazoncorretto-8-debian`, `3-amazoncorretto-8-debian-trixie`](https://github.com/carlossg/docker-maven/blob/5557ed7695b311b7880b5094dbedcb759dddd86a/amazoncorretto-8-debian/Dockerfile)
 
--	[`3.9.11-sapmachine-11`, `3.9-sapmachine-11`, `3-sapmachine-11`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/sapmachine-11/Dockerfile)
-
 -	[`3.9.11-sapmachine-17`, `3.9-sapmachine-17`, `3-sapmachine-17`](https://github.com/carlossg/docker-maven/blob/6bd15f0c704bad9806b4bbedea6f1faff5194c71/sapmachine-17/Dockerfile)
 
 -	[`4.0.0-rc-4-sapmachine-17`](https://github.com/carlossg/docker-maven/blob/3e68954f87f8b9be35921fdd538c4d769362f3bf/sapmachine-17-maven-4/Dockerfile)
@@ -188,7 +178,7 @@ WARNING:
 You can run a Maven project by using the Maven Docker image directly, passing a Maven command to `docker run`:
 
 ```console
-$ docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.3-jdk-8 mvn clean install
+$ docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven arm64v8/maven:3.3-jdk-8 mvn clean install
 ```
 
 ## Building local Docker image (optional)
@@ -196,7 +186,7 @@ $ docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /u
 This is a base image that you can extend, so it has the bare minimum packages needed. If you add custom package(s) to the `Dockerfile`, then you can build your local Docker image like this:
 
 ```console
-$ docker build --tag my_local_maven:3.5.2-jdk-8 .
+$ docker build --tag my_local_arm64v8/maven:3.5.2-jdk-8 .
 ```
 
 # Reusing the Maven local repository
@@ -205,14 +195,14 @@ The local Maven repository can be reused across containers by creating a volume
 
 ```console
 $ docker volume create --name maven-repo
-$ docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will download artifacts
-$ docker run -it -v maven-repo:/root/.m2 maven mvn archetype:generate # will reuse downloaded artifacts
+$ docker run -it -v maven-repo:/root/.m2 arm64v8/maven mvn archetype:generate # will download artifacts
+$ docker run -it -v maven-repo:/root/.m2 arm64v8/maven mvn archetype:generate # will reuse downloaded artifacts
 ```
 
 Or you can just use your home .m2 cache directory that you share e.g. with your Eclipse/IDEA:
 
 ```console
-$ docker run -it --rm -v "$PWD":/usr/src/mymaven -v "$HOME/.m2":/root/.m2 -v "$PWD/target:/usr/src/mymaven/target" -w /usr/src/mymaven maven mvn clean package  
+$ docker run -it --rm -v "$PWD":/usr/src/mymaven -v "$HOME/.m2":/root/.m2 -v "$PWD/target:/usr/src/mymaven/target" -w /usr/src/mymaven arm64v8/maven mvn clean package  
 ```
 
 # Packaging a local repository with the image
@@ -241,14 +231,14 @@ Maven needs the user home to download artifacts to, and if the user does not exi
 For example, to run as user `1000` mounting the host' Maven repo
 
 ```console
-$ docker run -v ~/.m2:/var/maven/.m2 -ti --rm -u 1000 -e MAVEN_CONFIG=/var/maven/.m2 maven mvn -Duser.home=/var/maven archetype:generate
+$ docker run -v ~/.m2:/var/maven/.m2 -ti --rm -u 1000 -e MAVEN_CONFIG=/var/maven/.m2 arm64v8/maven mvn -Duser.home=/var/maven archetype:generate
 ```
 
 # Image Variants
 
-The `maven` images come in many flavors, each designed for a specific use case.
+The `arm64v8/maven` images come in many flavors, each designed for a specific use case.
 
-## `maven:<version>`
+## `arm64v8/maven:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
@@ -256,7 +246,7 @@ Some of these tags may have names like trixie in them. These are the suite code
 
 Some of these tags may have names like noble in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
 
-## `maven:<version>-alpine`
+## `arm64v8/maven:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

mediawiki/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `mediawiki` official image](https://hub.docker.com/_/mediawiki) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -74,13 +76,13 @@ MediaWiki is free and open-source wiki software. Originally developed by Magnus
 The basic pattern for starting a `mediawiki` instance is:
 
 ```console
-$ docker run --name some-mediawiki -d mediawiki
+$ docker run --name some-mediawiki -d arm64v8/mediawiki
 ```
 
 If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used:
 
 ```console
-$ docker run --name some-mediawiki -p 8080:80 -d mediawiki
+$ docker run --name some-mediawiki -p 8080:80 -d arm64v8/mediawiki
 ```
 
 Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browser.
@@ -92,7 +94,7 @@ When first accessing the webserver provided by this image, it will go through a
 ## MySQL
 
 ```console
-$ docker run --name some-mediawiki --link some-mysql:mysql -d mediawiki
+$ docker run --name some-mediawiki --link some-mysql:mysql -d arm64v8/mediawiki
 ```
 
 -	Database type: `MySQL, MariaDB, or equivalent`
@@ -106,7 +108,7 @@ By default, this image does not include any volumes.
 The paths `/var/www/html/images` and `/var/www/html/LocalSettings.php` are things that generally ought to be volumes, but do not explicitly have a `VOLUME` declaration in this image because volumes cannot be removed.
 
 ```console
-$ docker run --rm mediawiki tar -cC /var/www/html/sites . | tar -xC /path/on/host/sites
+$ docker run --rm arm64v8/mediawiki tar -cC /var/www/html/sites . | tar -xC /path/on/host/sites
 ```
 
 ## ... via [`docker compose`](https://github.com/docker/compose)
@@ -162,13 +164,13 @@ The following Docker Hub features can help with the task of keeping your depende
 
 # Image Variants
 
-The `mediawiki` images come in many flavors, each designed for a specific use case.
+The `arm64v8/mediawiki` images come in many flavors, each designed for a specific use case.
 
-## `mediawiki:<version>`
+## `arm64v8/mediawiki:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `mediawiki:<version>-alpine`
+## `arm64v8/mediawiki:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

memcached/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `memcached` official image](https://hub.docker.com/_/memcached) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -58,7 +60,7 @@ Memcached's APIs provide a very large hash table distributed across multiple mac
 # How to use this image
 
 ```console
-$ docker run --name my-memcache -d memcached
+$ docker run --name my-memcache -d arm64v8/memcached
 ```
 
 ### Configuration
@@ -66,13 +68,13 @@ $ docker run --name my-memcache -d memcached
 To customize the configuration of the memcached server, first obtain the upstream configuration options from the container:
 
 ```console
-$ docker run --rm memcached -h
+$ docker run --rm arm64v8/memcached -h
 ```
 
 Using `docker run`:
 
 ```console
-$ docker run --name my-memcache -d memcached memcached --memory-limit=64
+$ docker run --name my-memcache -d arm64v8/memcached memcached --memory-limit=64
 ```
 
 or using Docker Compose:
@@ -80,7 +82,7 @@ or using Docker Compose:
 ```yaml
 services:
   memcached:
-    image: memcached
+    image: arm64v8/memcached
     command:
       - --conn-limit=1024
       - --memory-limit=64
@@ -91,15 +93,15 @@ For infomation on configuring your memcached server, see the extensive [wiki](ht
 
 # Image Variants
 
-The `memcached` images come in many flavors, each designed for a specific use case.
+The `arm64v8/memcached` images come in many flavors, each designed for a specific use case.
 
-## `memcached:<version>`
+## `arm64v8/memcached:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `memcached:<version>-alpine`
+## `arm64v8/memcached:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

mongo-express/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `mongo-express` official image](https://hub.docker.com/_/mongo-express) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,7 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
-**No supported tags**
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -56,7 +58,7 @@ mongo-express is a web-based MongoDB admin interface written in Node.js, Express
 # How to use this image
 
 ```console
-$ docker run --network some-network -e ME_CONFIG_MONGODB_SERVER=some-mongo -p 8081:8081 mongo-express
+$ docker run --network some-network -e ME_CONFIG_MONGODB_SERVER=some-mongo -p 8081:8081 arm64v8/mongo-express
 ```
 
 Then you can hit `http://localhost:8081` or `http://host-ip:8081` in your browser.
@@ -108,7 +110,7 @@ $ docker run -it --rm \
     -e ME_CONFIG_MONGODB_SERVER="web_db_1" \
     -e ME_CONFIG_BASICAUTH_USERNAME="user" \
     -e ME_CONFIG_BASICAUTH_PASSWORD="fairly long password" \
-    mongo-express
+    arm64v8/mongo-express
 ```
 
 This example links to a container name typical of `docker compose`, changes the editor's color theme, and enables basic authentication.

mongo/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `mongo` official image](https://hub.docker.com/_/mongo) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -30,74 +32,23 @@ WARNING:
 
 -	[`8.0.15-noble`, `8.0-noble`, `8-noble`, `noble`](https://github.com/docker-library/mongo/blob/12330e190aa0ba8cfd07004a7a74791b270a3206/8.0/Dockerfile)
 
--	[`8.0.15-windowsservercore-ltsc2025`, `8.0-windowsservercore-ltsc2025`, `8-windowsservercore-ltsc2025`, `windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`8.0.15-windowsservercore-ltsc2022`, `8.0-windowsservercore-ltsc2022`, `8-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`8.0.15-nanoserver-ltsc2022`, `8.0-nanoserver-ltsc2022`, `8-nanoserver-ltsc2022`, `nanoserver-ltsc2022`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`7.0.25-jammy`, `7.0-jammy`, `7-jammy`](https://github.com/docker-library/mongo/blob/12330e190aa0ba8cfd07004a7a74791b270a3206/7.0/Dockerfile)
 
--	[`7.0.25-windowsservercore-ltsc2025`, `7.0-windowsservercore-ltsc2025`, `7-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`7.0.25-windowsservercore-ltsc2022`, `7.0-windowsservercore-ltsc2022`, `7-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`7.0.25-nanoserver-ltsc2022`, `7.0-nanoserver-ltsc2022`, `7-nanoserver-ltsc2022`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/nanoserver-ltsc2022/Dockerfile)
-
 -	[`6.0.26-jammy`, `6.0-jammy`, `6-jammy`](https://github.com/docker-library/mongo/blob/d9efcb7f46c4a17da2fdc9dbb4ef644f4f92053d/6.0/Dockerfile)
 
--	[`6.0.26-windowsservercore-ltsc2025`, `6.0-windowsservercore-ltsc2025`, `6-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`6.0.26-windowsservercore-ltsc2022`, `6.0-windowsservercore-ltsc2022`, `6-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`6.0.26-nanoserver-ltsc2022`, `6.0-nanoserver-ltsc2022`, `6-nanoserver-ltsc2022`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/nanoserver-ltsc2022/Dockerfile)
-
 ## Shared Tags
 
 -	`8.0.15`, `8.0`, `8`, `latest`:
 
 	-	[`8.0.15-noble`](https://github.com/docker-library/mongo/blob/12330e190aa0ba8cfd07004a7a74791b270a3206/8.0/Dockerfile)
-	-	[`8.0.15-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`8.0.15-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`8.0.15-windowsservercore`, `8.0-windowsservercore`, `8-windowsservercore`, `windowsservercore`:
-
-	-	[`8.0.15-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`8.0.15-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`8.0.15-nanoserver`, `8.0-nanoserver`, `8-nanoserver`, `nanoserver`:
-
-	-	[`8.0.15-nanoserver-ltsc2022`](https://github.com/docker-library/mongo/blob/c7ea10a79db9577890466804058872f34f21b3ab/8.0/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`7.0.25`, `7.0`, `7`:
 
 	-	[`7.0.25-jammy`](https://github.com/docker-library/mongo/blob/12330e190aa0ba8cfd07004a7a74791b270a3206/7.0/Dockerfile)
-	-	[`7.0.25-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`7.0.25-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`7.0.25-windowsservercore`, `7.0-windowsservercore`, `7-windowsservercore`:
-
-	-	[`7.0.25-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`7.0.25-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`7.0.25-nanoserver`, `7.0-nanoserver`, `7-nanoserver`:
-
-	-	[`7.0.25-nanoserver-ltsc2022`](https://github.com/docker-library/mongo/blob/d828bd4b9677891b7b4a5a2259d939f7a5cb3377/7.0/windows/nanoserver-ltsc2022/Dockerfile)
 
 -	`6.0.26`, `6.0`, `6`:
 
 	-	[`6.0.26-jammy`](https://github.com/docker-library/mongo/blob/d9efcb7f46c4a17da2fdc9dbb4ef644f4f92053d/6.0/Dockerfile)
-	-	[`6.0.26-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`6.0.26-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`6.0.26-windowsservercore`, `6.0-windowsservercore`, `6-windowsservercore`:
-
-	-	[`6.0.26-windowsservercore-ltsc2025`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`6.0.26-windowsservercore-ltsc2022`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`6.0.26-nanoserver`, `6.0-nanoserver`, `6-nanoserver`:
-
-	-	[`6.0.26-nanoserver-ltsc2022`](https://github.com/docker-library/mongo/blob/0bd4b9bbe4bb9b85a56b851516a6c36a4629743b/6.0/windows/nanoserver-ltsc2022/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -137,7 +88,7 @@ By default Mongo's configuration requires no authentication for access, even for
 ## Start a `mongo` server instance
 
 ```console
-$ docker run --name some-mongo -d mongo:tag
+$ docker run --name some-mongo -d arm64v8/mongo:tag
 ```
 
 ... where `some-mongo` is the name you want to assign to your container and `tag` is the tag specifying the MongoDB version you want. See the list above for relevant tags.
@@ -147,7 +98,7 @@ $ docker run --name some-mongo -d mongo:tag
 The MongoDB server in the image listens on the standard MongoDB port, `27017`, so connecting via Docker networks will be the same as connecting to a remote `mongod`. The following example starts another MongoDB container instance and runs the `mongosh` (use `mongo` with `4.x` versions) command line client against the original MongoDB container from the example above, allowing you to execute MongoDB statements against your database instance:
 
 ```console
-$ docker run -it --network some-network --rm mongo mongosh --host some-mongo test
+$ docker run -it --network some-network --rm arm64v8/mongo mongosh --host some-mongo test
 ```
 
 ... where `some-mongo` is the name of your original `mongo` container.
@@ -181,7 +132,7 @@ Run `docker compose up`, wait for it to initialize completely, and visit `http:/
 
 ## Container shell access and viewing MongoDB logs
 
-The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `mongo` container:
+The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `arm64v8/mongo` container:
 
 ```console
 $ docker exec -it some-mongo bash
@@ -202,7 +153,7 @@ See the [MongoDB manual](https://www.mongodb.com/docs/manual/administration/conf
 Most MongoDB configuration options can be set through flags to `mongod`. The entrypoint of the image passes its arguments along to `mongod`. Example below enables MongoDB [query profiler](https://www.mongodb.com/docs/manual/reference/program/mongod/#profiler-options) via `docker run`.
 
 ```console
-$ docker run --name some-mongo -d mongo --profile 1
+$ docker run --name some-mongo -d arm64v8/mongo --profile 1
 ```
 
 The same can be achieved with a `compose.yaml` file
@@ -210,24 +161,24 @@ The same can be achieved with a `compose.yaml` file
 ```yaml
 services:
   mongo:
-    image: mongo
+    image: arm64v8/mongo
     command: --profile 1
 ```
 
 To see the full list of possible options, check the MongoDB manual on [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod/) or check the `--help` output of `mongod`:
 
 ```console
-$ docker run -it --rm mongo --help
+$ docker run -it --rm arm64v8/mongo --help
 ```
 
 ## Using a custom MongoDB configuration file
 
-For a more complicated configuration setup, you can still use the MongoDB configuration file. `mongod` does not read a configuration file by default, so the `--config` option with the path to the configuration file needs to be specified. Create a custom configuration file and put it in the container by either creating a custom Dockerfile `FROM mongo` or mounting it from the host machine to the container. See the MongoDB manual for a full list of [configuration file](https://www.mongodb.com/docs/manual/reference/configuration-options/) options.
+For a more complicated configuration setup, you can still use the MongoDB configuration file. `mongod` does not read a configuration file by default, so the `--config` option with the path to the configuration file needs to be specified. Create a custom configuration file and put it in the container by either creating a custom Dockerfile `FROM arm64v8/mongo` or mounting it from the host machine to the container. See the MongoDB manual for a full list of [configuration file](https://www.mongodb.com/docs/manual/reference/configuration-options/) options.
 
 For example, `/my/custom/mongod.conf` is the path to the custom configuration file. Then start the MongoDB container like the following:
 
 ```console
-$ docker run --name some-mongo -v /my/custom:/etc/mongo -d mongo --config /etc/mongo/mongod.conf
+$ docker run --name some-mongo -v /my/custom:/etc/mongo -d arm64v8/mongo --config /etc/mongo/mongod.conf
 ```
 
 ## Environment Variables
@@ -244,9 +195,9 @@ The following is an example of using these two variables to create a MongoDB ins
 $ docker run -d --network some-network --name some-mongo \
 	-e MONGO_INITDB_ROOT_USERNAME=mongoadmin \
 	-e MONGO_INITDB_ROOT_PASSWORD=secret \
-	mongo
+	arm64v8/mongo
 
-$ docker run -it --rm --network some-network mongo \
+$ docker run -it --rm --network some-network arm64v8/mongo \
 	mongosh --host some-mongo \
 		-u mongoadmin \
 		-p secret \
@@ -269,7 +220,7 @@ This variable allows you to specify the name of a database to be used for creati
 As an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in `/run/secrets/<secret_name>` files. For example:
 
 ```console
-$ docker run --name some-mongo -e MONGO_INITDB_ROOT_PASSWORD_FILE=/run/secrets/mongo-root -d mongo
+$ docker run --name some-mongo -e MONGO_INITDB_ROOT_PASSWORD_FILE=/run/secrets/mongo-root -d arm64v8/mongo
 ```
 
 Currently, this is only supported for `MONGO_INITDB_ROOT_USERNAME` and `MONGO_INITDB_ROOT_PASSWORD`.
@@ -307,7 +258,7 @@ The Docker documentation is a good starting point for understanding the differen
 2.	Start your `mongo` container like this:
 
 	```console
-	$ docker run --name some-mongo -v /my/own/datadir:/data/db -d mongo
+	$ docker run --name some-mongo -v /my/own/datadir:/data/db -d arm64v8/mongo
 	```
 
 The `-v /my/own/datadir:/data/db` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/data/db` inside the container, where MongoDB by default will write its data files.
@@ -322,24 +273,6 @@ Most of the normal tools will work, although their usage might be a little convo
 $ docker exec some-mongo sh -c 'exec mongodump -d <database_name> --archive' > /some/path/on/your/host/all-collections.archive
 ```
 
-# Image Variants
-
-The `mongo` images come in many flavors, each designed for a specific use case.
-
-## `mongo:<version>`
-
-This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
-
-Some of these tags may have names like jammy or noble in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
-
-## `mongo:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
 # License
 
 View [license information](https://github.com/mongodb/mongo/blob/6ea81c883e7297be99884185c908c7ece385caf8/README#L89-L95) for the software contained in this image.

monica/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `monica` official image](https://hub.docker.com/_/monica) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -74,7 +76,7 @@ The `fpm` tag contains a fastCGI-Process that serves the web pages. This image s
 This image contains a webserver that exposes port 80. Run the container with:
 
 ```console
-docker run --name some-monica -d -p 8080:80 monica
+docker run --name some-monica -d -p 8080:80 arm64v8/monica
 ```
 
 ### Using the fpm image
@@ -82,7 +84,7 @@ docker run --name some-monica -d -p 8080:80 monica
 This image serves a fastCGI server that exposes port 9000. You may need an additional web server that can proxy requests to the fpm port 9000 of the container. Run this container with:
 
 ```console
-docker run --name some-monica -d -p 9000:9000 monica:fpm
+docker run --name some-monica -d -p 9000:9000 arm64v8/monica:fpm
 ```
 
 ### Using an external database
@@ -98,7 +100,7 @@ Run a container with this named volume:
 ```console
 docker run -d \
         -v monica_data:/var/www/html/storage \
-        monica
+        arm64v8/monica
 ```
 
 ### Run commands inside the container
@@ -275,13 +277,13 @@ See some examples of Docker Compose possibilities in the [example section](https
 
 # Image Variants
 
-The `monica` images come in many flavors, each designed for a specific use case.
+The `arm64v8/monica` images come in many flavors, each designed for a specific use case.
 
-## `monica:<version>`
+## `arm64v8/monica:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `monica:<version>-alpine`
+## `arm64v8/monica:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

mysql/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `mysql` official image](https://hub.docker.com/_/mysql) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -30,8 +32,6 @@ WARNING:
 
 -	[`8.0.43`, `8.0`, `8.0.43-oraclelinux9`, `8.0-oraclelinux9`, `8.0.43-oracle`, `8.0-oracle`](https://github.com/docker-library/mysql/blob/7a5e9fbb739c7d423437b8687dfd400ea84fdb20/8.0/Dockerfile.oracle)
 
--	[`8.0.43-bookworm`, `8.0-bookworm`, `8.0.43-debian`, `8.0-debian`](https://github.com/docker-library/mysql/blob/7a5e9fbb739c7d423437b8687dfd400ea84fdb20/8.0/Dockerfile.debian)
-
 # Quick reference (cont.)
 
 -	**Where to file issues**:  
@@ -61,30 +61,30 @@ For more information and related downloads for MySQL Server and other MySQL prod
 
 # How to use this image
 
-## Start a `mysql` server instance
+## Start a `arm64v8/mysql` server instance
 
 Starting a MySQL instance is simple:
 
 ```console
-$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag
+$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/mysql:tag
 ```
 
 ... where `some-mysql` is the name you want to assign to your container, `my-secret-pw` is the password to be set for the MySQL root user and `tag` is the tag specifying the MySQL version you want. See the list above for relevant tags.
 
 ## Connect to MySQL from the MySQL command line client
 
-The following command starts another `mysql` container instance and runs the `mysql` command line client against your original `mysql` container, allowing you to execute SQL statements against your database instance:
+The following command starts another `arm64v8/mysql` container instance and runs the `mysql` command line client against your original `arm64v8/mysql` container, allowing you to execute SQL statements against your database instance:
 
 ```console
-$ docker run -it --network some-network --rm mysql mysql -hsome-mysql -uexample-user -p
+$ docker run -it --network some-network --rm arm64v8/mysql mysql -hsome-mysql -uexample-user -p
 ```
 
-... where `some-mysql` is the name of your original `mysql` container (connected to the `some-network` Docker network).
+... where `some-mysql` is the name of your original `arm64v8/mysql` container (connected to the `some-network` Docker network).
 
 This image can also be used as a client for non-Docker or remote instances:
 
 ```console
-$ docker run -it --rm mysql mysql -hsome.mysql.host -usome-mysql-user -p
+$ docker run -it --rm arm64v8/mysql mysql -hsome.mysql.host -usome-mysql-user -p
 ```
 
 More information about the MySQL command line client can be found in the [MySQL documentation](http://dev.mysql.com/doc/en/mysql.html)
@@ -110,7 +110,7 @@ Run `docker compose up`, wait for it to initialize completely, and visit `http:/
 
 ## Container shell access and viewing MySQL logs
 
-The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `mysql` container:
+The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `arm64v8/mysql` container:
 
 ```console
 $ docker exec -it some-mysql bash
@@ -130,12 +130,12 @@ The default configuration for MySQL varies depending on the base image:
 
 **Debian-based MySQL 8 images:** The default configuration can be found in `/etc/mysql/my.cnf`, which may `!includedir` additional directories such as `/etc/mysql/conf.d`.
 
-Please inspect the relevant files and directories within the `mysql` image itself for more details.
+Please inspect the relevant files and directories within the `arm64v8/mysql` image itself for more details.
 
-If `/my/custom/config-file.cnf` is the path and name of your custom configuration file, you can start your `mysql` container like this (note that only the directory path of the custom config file is used in this command):
+If `/my/custom/config-file.cnf` is the path and name of your custom configuration file, you can start your `arm64v8/mysql` container like this (note that only the directory path of the custom config file is used in this command):
 
 ```console
-$ docker run --name some-mysql -v /my/custom:/etc/mysql/conf.d -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag
+$ docker run --name some-mysql -v /my/custom:/etc/mysql/conf.d -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/mysql:tag
 ```
 
 This will start a new container `some-mysql` where the MySQL instance uses the combined startup settings from the default configuration file and `/etc/mysql/conf.d/config-file.cnf`, with settings from the latter taking precedence.
@@ -145,18 +145,18 @@ This will start a new container `some-mysql` where the MySQL instance uses the c
 Many configuration options can be passed as flags to `mysqld`. This will give you the flexibility to customize the container without needing a `cnf` file. For example, if you want to change the default encoding and collation for all tables to use UTF-8 (`utf8mb4`) just run the following:
 
 ```console
-$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/mysql:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
 ```
 
 If you would like to see a complete list of available options, just run:
 
 ```console
-$ docker run -it --rm mysql:tag --verbose --help
+$ docker run -it --rm arm64v8/mysql:tag --verbose --help
 ```
 
 ## Environment Variables
 
-When you start the `mysql` image, you can adjust the configuration of the MySQL instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.
+When you start the `arm64v8/mysql` image, you can adjust the configuration of the MySQL instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.
 
 See also https://dev.mysql.com/doc/refman/5.7/en/environment-variables.html for documentation of environment variables which MySQL itself respects (especially variables like `MYSQL_HOST`, which is known to cause issues when used with this image).
 
@@ -195,7 +195,7 @@ By default, the entrypoint script automatically loads the timezone data needed f
 As an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in `/run/secrets/<secret_name>` files. For example:
 
 ```console
-$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql-root -d mysql:tag
+$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql-root -d arm64v8/mysql:tag
 ```
 
 Currently, this is only supported for `MYSQL_ROOT_PASSWORD`, `MYSQL_ROOT_HOST`, `MYSQL_DATABASE`, `MYSQL_USER`, and `MYSQL_PASSWORD`.
@@ -204,13 +204,13 @@ Currently, this is only supported for `MYSQL_ROOT_PASSWORD`, `MYSQL_ROOT_HOST`,
 
 When a container is started for the first time, a new database with the specified name will be created and initialized with the provided configuration variables. Furthermore, it will execute files with extensions `.sh`, `.sql`, `.sql.gz`, `.sql.bz2`, `.sql.xz`, and `.sql.zst` that are found in `/docker-entrypoint-initdb.d`. Files will be executed in alphabetical order. When parsing `.sh` files without the execute bit set, they are `source`d rather than executed.
 
-You can easily populate your `mysql` services by [mounting a SQL dump into that directory](https://docs.docker.com/storage/bind-mounts/) and provide [custom images](https://docs.docker.com/reference/dockerfile/) with contributed data. SQL files will be imported by default to the database specified by the `MYSQL_DATABASE` variable.
+You can easily populate your `arm64v8/mysql` services by [mounting a SQL dump into that directory](https://docs.docker.com/storage/bind-mounts/) and provide [custom images](https://docs.docker.com/reference/dockerfile/) with contributed data. SQL files will be imported by default to the database specified by the `MYSQL_DATABASE` variable.
 
 # Caveats
 
 ## Where to Store Data
 
-Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `mysql` images to familiarize themselves with the options available, including:
+Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `arm64v8/mysql` images to familiarize themselves with the options available, including:
 
 -	Let Docker manage the storage of your database data [by writing the database files to disk on the host system using its own internal volume management](https://docs.docker.com/storage/volumes/). This is the default and is easy and fairly transparent to the user. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers.
 -	Create a data directory on the host system (outside the container) and [mount this to a directory visible from inside the container](https://docs.docker.com/storage/bind-mounts/). This places the database files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly.
@@ -218,10 +218,10 @@ Important note: There are several ways to store data used by applications that r
 The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:
 
 1.	Create a data directory on a suitable volume on your host system, e.g. `/my/own/datadir`.
-2.	Start your `mysql` container like this:
+2.	Start your `arm64v8/mysql` container like this:
 
 	```console
-	$ docker run --name some-mysql -v /my/own/datadir:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag
+	$ docker run --name some-mysql -v /my/own/datadir:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/mysql:tag
 	```
 
 The `-v /my/own/datadir:/var/lib/mysql` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/mysql` inside the container, where MySQL by default will write its data files.
@@ -234,7 +234,7 @@ If the application you're trying to connect to MySQL does not handle MySQL downt
 
 ## Usage against an existing database
 
-If you start your `mysql` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), the `$MYSQL_ROOT_PASSWORD` variable should be omitted from the run command line; it will in any case be ignored, and the pre-existing database will not be changed in any way.
+If you start your `arm64v8/mysql` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), the `$MYSQL_ROOT_PASSWORD` variable should be omitted from the run command line; it will in any case be ignored, and the pre-existing database will not be changed in any way.
 
 ## Running as an arbitrary user
 
@@ -244,7 +244,7 @@ If you know the permissions of your directory are already set appropriately (suc
 $ mkdir data
 $ ls -lnd data
 drwxr-xr-x 2 1000 1000 4096 Aug 27 15:54 data
-$ docker run -v "$PWD/data":/var/lib/mysql --user 1000:1000 --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag
+$ docker run -v "$PWD/data":/var/lib/mysql --user 1000:1000 --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/mysql:tag
 ```
 
 ## Creating database dumps

nats/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `nats` official image](https://hub.docker.com/_/nats) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -32,66 +34,27 @@ WARNING:
 
 -	[`2.12.1-scratch`, `2.12-scratch`, `2-scratch`, `scratch`, `2.12.1-linux`, `2.12-linux`, `2-linux`, `linux`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/scratch/Dockerfile)
 
--	[`2.12.1-windowsservercore-ltsc2022`, `2.12-windowsservercore-ltsc2022`, `2-windowsservercore-ltsc2022`, `windowsservercore-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/windowsservercore-ltsc2022/Dockerfile)
-
--	[`2.12.1-nanoserver-ltsc2022`, `2.12-nanoserver-ltsc2022`, `2-nanoserver-ltsc2022`, `nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/nanoserver-ltsc2022/Dockerfile)
-
 -	[`2.11.10-alpine3.22`, `2.11-alpine3.22`, `2.11.10-alpine`, `2.11-alpine`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/alpine3.22/Dockerfile)
 
 -	[`2.11.10-scratch`, `2.11-scratch`, `2.11.10-linux`, `2.11-linux`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/scratch/Dockerfile)
 
--	[`2.11.10-windowsservercore-ltsc2022`, `2.11-windowsservercore-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/windowsservercore-ltsc2022/Dockerfile)
-
--	[`2.11.10-nanoserver-ltsc2022`, `2.11-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/nanoserver-ltsc2022/Dockerfile)
-
 -	[`2.10.29-alpine3.22`, `2.10-alpine3.22`, `2.10.29-alpine`, `2.10-alpine`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/alpine3.22/Dockerfile)
 
 -	[`2.10.29-scratch`, `2.10-scratch`, `2.10.29-linux`, `2.10-linux`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/scratch/Dockerfile)
 
--	[`2.10.29-windowsservercore-ltsc2022`, `2.10-windowsservercore-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/windowsservercore-ltsc2022/Dockerfile)
-
--	[`2.10.29-nanoserver-ltsc2022`, `2.10-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/nanoserver-ltsc2022/Dockerfile)
-
 ## Shared Tags
 
 -	`2.12.1`, `2.12`, `2`, `latest`:
 
 	-	[`2.12.1-scratch`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/scratch/Dockerfile)
-	-	[`2.12.1-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/nanoserver-ltsc2022/Dockerfile)
-
--	`2.12.1-windowsservercore`, `2.12-windowsservercore`, `2-windowsservercore`, `windowsservercore`:
-
-	-	[`2.12.1-windowsservercore-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/windowsservercore-ltsc2022/Dockerfile)
-
--	`2.12.1-nanoserver`, `2.12-nanoserver`, `2-nanoserver`, `nanoserver`:
-
-	-	[`2.12.1-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.12.x/nanoserver-ltsc2022/Dockerfile)
 
 -	`2.11.10`, `2.11`:
 
 	-	[`2.11.10-scratch`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/scratch/Dockerfile)
-	-	[`2.11.10-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/nanoserver-ltsc2022/Dockerfile)
-
--	`2.11.10-windowsservercore`, `2.11-windowsservercore`:
-
-	-	[`2.11.10-windowsservercore-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/windowsservercore-ltsc2022/Dockerfile)
-
--	`2.11.10-nanoserver`, `2.11-nanoserver`:
-
-	-	[`2.11.10-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.11.x/nanoserver-ltsc2022/Dockerfile)
 
 -	`2.10.29`, `2.10`:
 
 	-	[`2.10.29-scratch`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/scratch/Dockerfile)
-	-	[`2.10.29-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/nanoserver-ltsc2022/Dockerfile)
-
--	`2.10.29-windowsservercore`, `2.10-windowsservercore`:
-
-	-	[`2.10.29-windowsservercore-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/windowsservercore-ltsc2022/Dockerfile)
-
--	`2.10.29-nanoserver`, `2.10-nanoserver`:
-
-	-	[`2.10.29-nanoserver-ltsc2022`](https://github.com/nats-io/nats-docker/blob/5b46acd148b1b7d13a084cca7fc1a50e75412360/2.10.x/nanoserver-ltsc2022/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -135,24 +98,24 @@ WARNING:
 # For instance, to run the NATS Server and have it listen on port 4444,
 # you would have to run like this:
 #
-#   docker run -p 4444:4444 nats -p 4444
+#   docker run -p 4444:4444 arm64v8/nats -p 4444
 #
 # Or, if you want to publish the port 4444 as a different port, for example 5555:
 #
-#   docker run -p 5555:4444 nats -p 4444
+#   docker run -p 5555:4444 arm64v8/nats -p 4444
 #
 # To enable NATS JetStream, use the -js flag:
 #
-#   docker run -p 4222:4222 nats -js
+#   docker run -p 4222:4222 arm64v8/nats -js
 #
 # And, to persist JetStream data to a volume you can use the -v and -sd flags.
 # Keep in mind that -v is a Docker flag, while -js and -sd are NATS Server flags:
 #
-#   docker run -p 4222:4222 -v nats:/data nats -js -sd /data
+#   docker run -p 4222:4222 -v nats:/data arm64v8/nats -js -sd /data
 #
 # Check "docker run" for more information.
 
-$ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats
+$ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 arm64v8/nats
 [INF] Starting nats-server
 [INF]   Version:  2.9.8
 [INF]   Git:      [60e335a]
@@ -171,10 +134,10 @@ $ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats
 # Note that since you are passing arguments, this overrides the CMD section
 # of the Dockerfile, so you need to pass all arguments, including the
 # config file.
-$ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats -c /etc/nats/nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222
+$ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 arm64v8/nats -c /etc/nats/nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222
 
 # If you want to verify the routes are connected, try this instead:
-$ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats -c /etc/nats/nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV
+$ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 arm64v8/nats -c /etc/nats/nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV
 [INF] Starting nats-server
 [INF]   Version:  2.9.8
 [INF]   Git:      [60e335a]
@@ -300,13 +263,13 @@ Common Options:
 
 # Image Variants
 
-The `nats` images come in many flavors, each designed for a specific use case.
+The `arm64v8/nats` images come in many flavors, each designed for a specific use case.
 
-## `nats:<version>`
+## `arm64v8/nats:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `nats:<version>-alpine`
+## `arm64v8/nats:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -314,14 +277,6 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `nats:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
 # License
 
 View [license information](https://github.com/nats-io/gnatsd/blob/master/LICENSE) for the software contained in this image.

neo4j/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `neo4j` official image](https://hub.docker.com/_/neo4j) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -77,7 +79,7 @@ You can start a Neo4j container like this:
 docker run \
     --publish=7474:7474 --publish=7687:7687 \
     --volume=$HOME/neo4j/data:/data \
-    neo4j
+    arm64v8/neo4j
 ```
 
 which allows you to access neo4j through your browser at [http://localhost:7474](http://localhost:7474).

neurodebian/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `neurodebian` official image](https://hub.docker.com/_/neurodebian) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -89,14 +91,14 @@ NeuroDebian images only add NeuroDebian repository and repository's GPG key. No
 
 `nd` tags are used to reflect suffixes used in versions of packages available from NeuroDebian.
 
-The `neurodebian:latest` tag will always point the Neurodebian-enabled latest stable release of Debian (which is, at the time of this writing, `debian:wheezy`).
+The `arm64v8/neurodebian:latest` tag will always point the Neurodebian-enabled latest stable release of Debian (which is, at the time of this writing, `debian:wheezy`).
 
 ## sources.list
 
 NeuroDebian APT file is installed under `/etc/apt/sources.list.d/neurodebian.sources.list` and currently enables only `main` (DFSG-compliant) area of the archive:
 
 ```console
-$ docker run neurodebian cat /etc/apt/sources.list.d/neurodebian.sources.list
+$ docker run arm64v8/neurodebian cat /etc/apt/sources.list.d/neurodebian.sources.list
 deb http://neuro.debian.net/debian wheezy main
 deb http://neuro.debian.net/debian data main
 #deb-src http://neuro.debian.net/debian-devel wheezy main

nextcloud/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `nextcloud` official image](https://hub.docker.com/_/nextcloud) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # IMPORTANT NOTE
 
 ⚠️⚠️⚠️ This image is maintained by community volunteers and designed for expert use. For quick and easy deployment that supports the full set of Nextcloud Hub features, use the [Nextcloud All-in-One docker container](https://github.com/nextcloud/all-in-one#nextcloud-all-in-one) maintained by Nextcloud GmbH.
@@ -86,7 +88,7 @@ The second option is a `fpm` container. It is based on the [php-fpm](https://hub
 The apache image contains a webserver and exposes port 80. To start the container type:
 
 ```console
-$ docker run -d -p 8080:80 nextcloud
+$ docker run -d -p 8080:80 arm64v8/nextcloud
 ```
 
 Now you can access Nextcloud at http://localhost:8080/ from your host system.
@@ -96,7 +98,7 @@ Now you can access Nextcloud at http://localhost:8080/ from your host system.
 To use the fpm image, you need an additional web server, such as [nginx](https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html), that can proxy http-request to the fpm-port of the container. For fpm connection this container exposes port 9000. In most cases, you might want to use another container or your host as proxy. If you use your host you can address your Nextcloud container directly on port 9000. If you use another container, make sure that you add them to the same docker network (via `docker run --network <NAME> ...` or a `compose.yaml` file). In both cases you don't want to map the fpm port to your host.
 
 ```console
-$ docker run -d nextcloud:fpm
+$ docker run -d arm64v8/nextcloud:fpm
 ```
 
 As the fastCGI-Process is not capable of serving static files (style sheets, images, ...), the webserver needs access to these files. This can be achieved with the `volumes-from` option. You can find more information in the Docker Compose section.
@@ -118,7 +120,7 @@ Nextcloud:
 ```console
 $ docker run -d \
 -v nextcloud:/var/www/html \
-nextcloud
+arm64v8/nextcloud
 ```
 
 Database:
@@ -153,7 +155,7 @@ $ docker run -d \
 -v config:/var/www/html/config \
 -v data:/var/www/html/data \
 -v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \
-nextcloud
+arm64v8/nextcloud
 ```
 
 ### Custom volumes
@@ -311,7 +313,7 @@ To use the hooks triggered by the `entrypoint` script, either
 ```yaml
 ...
   app:
-    image: nextcloud:stable
+    image: arm64v8/nextcloud:stable
 
     volumes:
       - ./app-hooks/pre-installation:/docker-entrypoint-hooks.d/pre-installation
@@ -372,7 +374,7 @@ services:
       - MYSQL_USER=nextcloud
 
   app:
-    image: nextcloud
+    image: arm64v8/nextcloud
     restart: always
     ports:
       - 8080:80
@@ -416,7 +418,7 @@ services:
       - MYSQL_USER=nextcloud
 
   app:
-    image: nextcloud:fpm
+    image: arm64v8/nextcloud:fpm
     restart: always
     links:
       - db
@@ -464,7 +466,7 @@ services:
       - postgres_user
 
   app:
-    image: nextcloud
+    image: arm64v8/nextcloud
     restart: always
     ports:
       - 8080:80
@@ -532,10 +534,10 @@ Updating the Nextcloud container is done by pulling the new image, throwing away
 Since all data is stored in volumes, nothing gets lost. The startup script will check for the version in your volume and the installed docker version. If it finds a mismatch, it automatically starts the upgrade process. Don't forget to add all the volumes to your new container, so it works as expected.
 
 ```console
-$ docker pull nextcloud
+$ docker pull arm64v8/nextcloud
 $ docker stop <your_nextcloud_container>
 $ docker rm <your_nextcloud_container>
-$ docker run <OPTIONS> -d nextcloud
+$ docker run <OPTIONS> -d arm64v8/nextcloud
 ```
 
 Beware that you have to run the same command with the options that you used to initially start your Nextcloud. That includes volumes, port mapping.
@@ -552,7 +554,7 @@ $ docker compose up -d
 A lot of people want to use additional functionality inside their Nextcloud installation. If the image does not include the packages you need, you can easily build your own image on top of it. Start your derived image with the `FROM` statement and add whatever you like.
 
 ```dockerfile
-FROM nextcloud:apache
+FROM arm64v8/nextcloud:apache
 
 RUN ...
 ```
@@ -576,7 +578,7 @@ If you use your own Dockerfile, you need to configure your `compose.yaml` file a
 If you intend to use another command to run the image, make sure that you set `NEXTCLOUD_UPDATE=1` in your Dockerfile. Otherwise the installation and update will not work.
 
 ```dockerfile
-FROM nextcloud:apache
+FROM arm64v8/nextcloud:apache
 
 ...
 
@@ -706,13 +708,13 @@ If you got any questions or problems using the image, please visit our [Github R
 
 # Image Variants
 
-The `nextcloud` images come in many flavors, each designed for a specific use case.
+The `arm64v8/nextcloud` images come in many flavors, each designed for a specific use case.
 
-## `nextcloud:<version>`
+## `arm64v8/nextcloud:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `nextcloud:<version>-alpine`
+## `arm64v8/nextcloud:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

nginx/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `nginx` official image](https://hub.docker.com/_/nginx) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -84,13 +86,13 @@ Nginx (pronounced "engine-x") is an open source reverse proxy server for HTTP, H
 ## Hosting some simple static content
 
 ```console
-$ docker run --name some-nginx -v /some/content:/usr/share/nginx/html:ro -d nginx
+$ docker run --name some-nginx -v /some/content:/usr/share/nginx/html:ro -d arm64v8/nginx
 ```
 
 Alternatively, a simple `Dockerfile` can be used to generate a new image that includes the necessary content (which is a much cleaner solution than the bind mount above):
 
 ```dockerfile
-FROM nginx
+FROM arm64v8/nginx
 COPY static-html-directory /usr/share/nginx/html
 ```
 
@@ -116,7 +118,7 @@ You can mount your configuration file, or build a new image with it.
 If you wish to adapt the default configuration, use something like the following to get it from a running nginx container:
 
 ```console
-$ docker run --rm --entrypoint=cat nginx /etc/nginx/nginx.conf > /host/path/nginx.conf
+$ docker run --rm --entrypoint=cat arm64v8/nginx /etc/nginx/nginx.conf > /host/path/nginx.conf
 ```
 
 And then edit `/host/path/nginx.conf` in your host file system.
@@ -126,13 +128,13 @@ For information on the syntax of the nginx configuration files, see [the officia
 ### Mount your configuration file
 
 ```console
-$ docker run --name my-custom-nginx-container -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d nginx
+$ docker run --name my-custom-nginx-container -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d arm64v8/nginx
 ```
 
 ### Build a new image with your configuration file
 
 ```dockerfile
-FROM nginx
+FROM arm64v8/nginx
 COPY nginx.conf /etc/nginx/nginx.conf
 ```
 
@@ -144,15 +146,15 @@ Then build the image with `docker build -t custom-nginx .` and run it as follows
 $ docker run --name my-custom-nginx-container -d custom-nginx
 ```
 
-### Using environment variables in nginx configuration (new in 1.19)
+### Using environment variables in arm64v8/nginx configuration (new in 1.19)
 
-Out-of-the-box, nginx doesn't support environment variables inside most configuration blocks. But this image has a function, which will extract environment variables before nginx starts.
+Out-of-the-box, arm64v8/nginx doesn't support environment variables inside most configuration blocks. But this image has a function, which will extract environment variables before arm64v8/nginx starts.
 
 Here is an example using `compose.yaml`:
 
 ```yaml
 web:
-  image: nginx
+  image: arm64v8/nginx
   volumes:
    - ./templates:/etc/nginx/templates
   ports:
@@ -186,29 +188,29 @@ This behavior can be changed via the following environment variables:
 		-	ex.) `/etc/nginx/templates/default.conf.template` will be output with the filename `/etc/nginx/conf.d/default.conf`.
 	-	This directory must be writable by the user running a container.
 
-## Running nginx in read-only mode
+## Running arm64v8/nginx in read-only mode
 
-To run nginx in read-only mode, you will need to mount a Docker volume to every location where nginx writes information. The default nginx configuration requires write access to `/var/cache/nginx` and `/var/run`. This can be easily accomplished by running nginx as follows:
+To run arm64v8/nginx in read-only mode, you will need to mount a Docker volume to every location where arm64v8/nginx writes information. The default arm64v8/nginx configuration requires write access to `/var/cache/nginx` and `/var/run`. This can be easily accomplished by running arm64v8/nginx as follows:
 
 ```console
 $ docker run -d -p 80:80 --read-only -v $(pwd)/nginx-cache:/var/cache/nginx -v $(pwd)/nginx-pid:/var/run nginx
 ```
 
-If you have a more advanced configuration that requires nginx to write to other locations, simply add more volume mounts to those locations.
+If you have a more advanced configuration that requires arm64v8/nginx to write to other locations, simply add more volume mounts to those locations.
 
 ## Running nginx in debug mode
 
 Images since version 1.9.8 come with `nginx-debug` binary that produces verbose output when using higher log levels. It can be used with simple CMD substitution:
 
 ```console
-$ docker run --name my-nginx -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d nginx nginx-debug -g 'daemon off;'
+$ docker run --name my-nginx -v /host/path/nginx.conf:/etc/nginx/nginx.conf:ro -d arm64v8/nginx nginx-debug -g 'daemon off;'
 ```
 
 Similar configuration in `compose.yaml` may look like this:
 
 ```yaml
 web:
-  image: nginx
+  image: arm64v8/nginx
   volumes:
     - ./nginx.conf:/etc/nginx/nginx.conf:ro
   command: [nginx-debug, '-g', 'daemon off;']
@@ -219,7 +221,7 @@ web:
 Since version 1.19.0, a verbose entrypoint was added. It provides information on what's happening during container startup. You can silence this output by setting environment variable `NGINX_ENTRYPOINT_QUIET_LOGS`:
 
 ```console
-$ docker run -d -e NGINX_ENTRYPOINT_QUIET_LOGS=1 nginx
+$ docker run -d -e NGINX_ENTRYPOINT_QUIET_LOGS=1 arm64v8/nginx
 ```
 
 ## User and group id
@@ -231,12 +233,12 @@ $ id
 uid=101(nginx) gid=101(nginx) groups=101(nginx)
 ```
 
-## Running nginx as a non-root user
+## Running arm64v8/nginx as a non-root user
 
-It is possible to run the image as a less privileged arbitrary UID/GID. This, however, requires modification of nginx configuration to use directories writeable by that specific UID/GID pair:
+It is possible to run the image as a less privileged arbitrary UID/GID. This, however, requires modification of arm64v8/nginx configuration to use directories writeable by that specific UID/GID pair:
 
 ```console
-$ docker run -d -v $PWD/nginx.conf:/etc/nginx/nginx.conf nginx
+$ docker run -d -v $PWD/nginx.conf:/etc/nginx/nginx.conf arm64v8/nginx
 ```
 
 where nginx.conf in the current directory should have the following directives re-defined:
@@ -262,19 +264,19 @@ Alternatively, check out the official [Docker NGINX unprivileged image](https://
 
 # Image Variants
 
-The `nginx` images come in many flavors, each designed for a specific use case.
+The `arm64v8/nginx` images come in many flavors, each designed for a specific use case.
 
-## `nginx:<version>`
+## `arm64v8/nginx:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `nginx:<version>-perl` / `nginx:<version>-alpine-perl`
+## `arm64v8/nginx:<version>-perl` / `arm64v8/nginx:<version>-alpine-perl`
 
-Starting with nginx:1.13.0 / mainline and nginx:1.12.0 / stable, the perl module has been removed from the default images. A separate `-perl` tag variant is available if you wish to use the perl module.
+Starting with arm64v8/nginx:1.13.0 / mainline and arm64v8/nginx:1.12.0 / stable, the perl module has been removed from the default images. A separate `-perl` tag variant is available if you wish to use the perl module.
 
-## `nginx:<version>-alpine`
+## `arm64v8/nginx:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -282,9 +284,9 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `nginx:<version>-slim`
+## `arm64v8/nginx:<version>-slim`
 
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `nginx`. Unless you are working in an environment where *only* the `nginx` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/nginx`. Unless you are working in an environment where *only* the `arm64v8/nginx` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
 
 # License
 

node/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `node` official image](https://hub.docker.com/_/node) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -125,9 +127,9 @@ See [How To Use This Image](https://github.com/nodejs/docker-node/blob/master/RE
 
 # Image Variants
 
-The `node` images come in many flavors, each designed for a specific use case.
+The `arm64v8/node` images come in many flavors, each designed for a specific use case.
 
-## `node:<version>`
+## `arm64v8/node:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
@@ -135,7 +137,7 @@ Some of these tags may have names like bookworm, bullseye, or trixie in them. Th
 
 This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
 
-## `node:<version>-alpine`
+## `arm64v8/node:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 
@@ -143,9 +145,9 @@ This variant is useful when final image size being as small as possible is your
 
 To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
 
-## `node:<version>-slim`
+## `arm64v8/node:<version>-slim`
 
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `node`. Unless you are working in an environment where *only* the `node` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/node`. Unless you are working in an environment where *only* the `arm64v8/node` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
 
 # License
 

notary/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `notary` official image](https://hub.docker.com/_/notary) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # **DEPRECATION NOTICE**
 
 The [upstream Notary project](https://github.com/notaryproject/notary) was archived as of July 30, 2025. For more information, see [notaryproject/.github#70](https://github.com/notaryproject/.github/issues/70).
@@ -28,7 +30,7 @@ The [upstream Notary project](https://github.com/notaryproject/notary) was archi
 
 # Supported tags and respective `Dockerfile` links
 
-**No supported tags**
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 

odoo/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `odoo` official image](https://hub.docker.com/_/odoo) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -70,7 +72,7 @@ $ docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=p
 ## Start an Odoo instance
 
 ```console
-$ docker run -p 8069:8069 --name odoo --link db:db -t odoo
+$ docker run -p 8069:8069 --name odoo --link db:db -t arm64v8/odoo
 ```
 
 The alias of the container running Postgres must be db for Odoo to be able to connect to the Postgres server.
@@ -78,8 +80,8 @@ The alias of the container running Postgres must be db for Odoo to be able to co
 ## Stop and restart an Odoo instance
 
 ```console
-$ docker stop odoo
-$ docker start -a odoo
+$ docker stop arm64v8/odoo
+$ docker start -a arm64v8/odoo
 ```
 
 ## Use named volumes to preserve data
@@ -87,7 +89,7 @@ $ docker start -a odoo
 When the Odoo container is created like described above, the odoo filestore is created inside the container. If the container is removed, the filestore is lost. The preferred way to prevent that is by using a Docker named [volume](https://docs.docker.com/storage/volumes/).
 
 ```console
-$ docker run -v odoo-data:/var/lib/odoo -d -p 8069:8069 --name odoo --link db:db -t odoo
+$ docker run -v odoo-data:/var/lib/odoo -d -p 8069:8069 --name odoo --link db:db -t arm64v8/odoo
 ```
 
 With the above command, the volume named `odoo-data` will persist even if the container is removed and can be re-used by issuing the same command.
@@ -111,7 +113,7 @@ Restarting a PostgreSQL server does not affect the created databases.
 The default configuration file for the server (located at `/etc/odoo/odoo.conf`) can be overriden at startup using volumes. Suppose you have a custom configuration at `/path/to/config/odoo.conf`, then
 
 ```console
-$ docker run -v /path/to/config:/etc/odoo -p 8069:8069 --name odoo --link db:db -t odoo
+$ docker run -v /path/to/config:/etc/odoo -p 8069:8069 --name odoo --link db:db -t arm64v8/odoo
 ```
 
 Please use [this configuration template](https://github.com/odoo/docker/blob/master/17.0/odoo.conf) to write your custom configuration as we already set some arguments for running Odoo inside a Docker container.
@@ -119,7 +121,7 @@ Please use [this configuration template](https://github.com/odoo/docker/blob/mas
 You can also directly specify Odoo arguments inline. Those arguments must be given after the keyword `--` in the command-line, as follows
 
 ```console
-$ docker run -p 8069:8069 --name odoo --link db:db -t odoo -- --db-filter=odoo_db_.*
+$ docker run -p 8069:8069 --name odoo --link db:db -t arm64v8/odoo -- --db-filter=odoo_db_.*
 ```
 
 ## Mount custom addons
@@ -127,7 +129,7 @@ $ docker run -p 8069:8069 --name odoo --link db:db -t odoo -- --db-filter=odoo_d
 You can mount your own Odoo addons within the Odoo container, at `/mnt/extra-addons`
 
 ```console
-$ docker run -v /path/to/addons:/mnt/extra-addons -p 8069:8069 --name odoo --link db:db -t odoo
+$ docker run -v /path/to/addons:/mnt/extra-addons -p 8069:8069 --name odoo --link db:db -t arm64v8/odoo
 ```
 
 **Note:** Altough there is no official Odoo Enterprise Docker image, the Enterprise modules can be mounted by using the above mentionned method.
@@ -135,8 +137,8 @@ $ docker run -v /path/to/addons:/mnt/extra-addons -p 8069:8069 --name odoo --lin
 ## Run multiple Odoo instances
 
 ```console
-$ docker run -p 8070:8069 --name odoo2 --link db:db -t odoo
-$ docker run -p 8071:8069 --name odoo3 --link db:db -t odoo
+$ docker run -p 8070:8069 --name odoo2 --link db:db -t arm64v8/odoo
+$ docker run -p 8071:8069 --name odoo3 --link db:db -t arm64v8/odoo
 ```
 
 **Note:** For plain use of mails and reports functionalities, when the host and container ports differ (e.g. 8070 and 8069), one has to set, in Odoo, `Settings->Parameters->System Parameters` (requires technical features), web.base.url to the container port (e.g. 127.0.0.1:8069).
@@ -157,7 +159,7 @@ The simplest `compose.yaml` file would be:
 ```yml
 services:
   web:
-    image: odoo:17.0
+    image: arm64v8/odoo:17.0
     depends_on:
       - db
     ports:
@@ -175,7 +177,7 @@ If the default postgres credentials does not suit you, tweak the environment var
 ```yml
 services:
   web:
-    image: odoo:17.0
+    image: arm64v8/odoo:17.0
     depends_on:
       - mydb
     ports:
@@ -202,7 +204,7 @@ Here's a last example showing you how to
 ```yml
 services:
   web:
-    image: odoo:17.0
+    image: arm64v8/odoo:17.0
     depends_on:
       - db
     ports:
@@ -250,7 +252,7 @@ Suppose you created a database from an Odoo instance named old-odoo, and you wan
 By default, Odoo 16.0+ uses a filestore (located at `/var/lib/odoo/filestore/`) for attachments. You should restore this filestore in your new Odoo instance by running
 
 ```console
-$ docker run --volumes-from old-odoo -p 8070:8069 --name new-odoo --link db:db -t odoo
+$ docker run --volumes-from old-odoo -p 8070:8069 --name new-odoo --link db:db -t arm64v8/odoo
 ```
 
 # License

open-liberty/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `open-liberty` official image](https://hub.docker.com/_/open-liberty) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -151,7 +153,7 @@ There are multiple tags available in this repository.
 The `kernel-slim` image contains just the Liberty kernel and no additional runtime features. This image is the recommended basis for custom built images, so that they can contain only the features required for a specific application. For example, the following Dockerfile starts with this image, copies in the `server.xml` that lists the features required by the application, and then uses the `features.sh` script to download those features from the online repository.
 
 ```dockerfile
-FROM open-liberty:kernel-slim
+FROM arm64v8/open-liberty:kernel-slim
 
 # Add server configuration
 COPY --chown=1001:0  server.xml /config/
@@ -194,7 +196,7 @@ When using `volumes`, an application file can be mounted in the `dropins` direct
 ```console
 $ docker run -d -p 80:9080 -p 443:9443 \
 	    -v /tmp/DefaultServletEngine/dropins/Sample1.war:/config/dropins/Sample1.war \
-	    open-liberty:full
+	    arm64v8/open-liberty:full
 ```
 
 When the server is started, you can browse to http://localhost/Sample1/SimpleServlet on the Docker host.
@@ -206,7 +208,7 @@ For greater flexibility over configuration, it is possible to mount an entire se
 ```console
 $ docker run -d -p 80:9080 \
   -v /tmp/DefaultServletEngine:/config \
-  open-liberty:full
+  arm64v8/open-liberty:full
 ```
 
 # Using Spring Boot with Open Liberty
@@ -218,7 +220,7 @@ To elaborate these capabilities this section assumes the standalone Spring Boot
 1.	A Spring Boot application JAR deploys to the `dropins/spring` directory within the default server configuration, not the `dropins` directory. Liberty allows one Spring Boot application per server configuration. You can create a Spring Boot application layer over this image by adding the application JAR to the `dropins/spring` directory. In this example we copied `hellospringboot.jar` from `/tmp` to the same directory containing the following Dockerfile.
 
 	```dockerfile
-	FROM open-liberty:kernel
+	FROM arm64v8/open-liberty:kernel
 
 	COPY --chown=1001:0 hellospringboot.jar /config/dropins/spring/
 	COPY --chown=1001:0 server.xml /config/
@@ -238,14 +240,14 @@ To elaborate these capabilities this section assumes the standalone Spring Boot
 	You can use the `springBootUtility` command to create thin application and library cache layers over a `full` image. The following example uses docker staging to efficiently build an image that deploys a fat Spring Boot application as two layers containing a thin application and a library cache.
 
 	```dockerfile
-	FROM open-liberty:kernel as staging
+	FROM arm64v8/open-liberty:kernel as staging
 	COPY --chown=1001:0 hellospringboot.jar /staging/myFatApp.jar
 	COPY --chown=1001:0 server.xml /config/
 	RUN springBootUtility thin \
 	   --sourceAppPath=/staging/myFatApp.jar \
 	   --targetThinAppPath=/staging/myThinApp.jar \
 	   --targetLibCachePath=/staging/lib.index.cache
-	FROM open-liberty:kernel
+	FROM arm64v8/open-liberty:kernel
 	COPY --chown=1001:0 server.xml /config
 	COPY --from=staging /staging/lib.index.cache /lib.index.cache
 	COPY --from=staging /staging/myThinApp.jar /config/dropins/spring/myThinApp.jar
@@ -285,7 +287,7 @@ Or, create a named data volume container that exposes a volume at the location o
 
 ```console
 docker run -v /opt/ol/wlp//output/.classCache \
-    --name classcache open-liberty true
+    --name classcache arm64v8/open-liberty true
 ```
 
 Then, run the Open Liberty image with the volumes from the data volume container classcache mounted as follows:
@@ -301,7 +303,7 @@ Liberty writes to two different directories when running: `/opt/ol/wlp//output`
 ```console
 docker run -d -p 80:9080 -p 443:9443 \
     --tmpfs /opt/ol/wlp//output --tmpfs /logs -v /config --read-only \
-    open-liberty:webProfile8
+    arm64v8/open-liberty:webProfile8
 ```
 
 # Relationship between Open Liberty and WebSphere Liberty
@@ -315,15 +317,15 @@ WebSphere Liberty is a commercial distribution of Open Liberty. There is an offi
 
 # Image Variants
 
-The `open-liberty` images come in many flavors, each designed for a specific use case.
+The `arm64v8/open-liberty` images come in many flavors, each designed for a specific use case.
 
-## `open-liberty:<version>`
+## `arm64v8/open-liberty:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `open-liberty:<version>-slim`
+## `arm64v8/open-liberty:<version>-slim`
 
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `open-liberty`. Unless you are working in an environment where *only* the `open-liberty` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/open-liberty`. Unless you are working in an environment where *only* the `arm64v8/open-liberty` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
 
 # License
 

openjdk/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `openjdk` official image](https://hub.docker.com/_/openjdk) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # **DEPRECATION NOTICE**
 
 This image is officially deprecated and all users are recommended to find and use suitable replacements ASAP. Some examples of other Official Image alternatives (listed in alphabetical order with no intentional or implied preference):
@@ -54,31 +56,11 @@ The only tags which will continue to receive updates beyond July 2022 will be Ea
 
 -	[`26-ea-19-jdk-slim-bookworm`, `26-ea-19-slim-bookworm`, `26-ea-jdk-slim-bookworm`, `26-ea-slim-bookworm`, `26-jdk-slim-bookworm`, `26-slim-bookworm`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/slim-bookworm/Dockerfile)
 
--	[`26-ea-19-jdk-windowsservercore-ltsc2025`, `26-ea-19-windowsservercore-ltsc2025`, `26-ea-jdk-windowsservercore-ltsc2025`, `26-ea-windowsservercore-ltsc2025`, `26-jdk-windowsservercore-ltsc2025`, `26-windowsservercore-ltsc2025`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-
--	[`26-ea-19-jdk-windowsservercore-ltsc2022`, `26-ea-19-windowsservercore-ltsc2022`, `26-ea-jdk-windowsservercore-ltsc2022`, `26-ea-windowsservercore-ltsc2022`, `26-jdk-windowsservercore-ltsc2022`, `26-windowsservercore-ltsc2022`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	[`26-ea-19-jdk-nanoserver-ltsc2025`, `26-ea-19-nanoserver-ltsc2025`, `26-ea-jdk-nanoserver-ltsc2025`, `26-ea-nanoserver-ltsc2025`, `26-jdk-nanoserver-ltsc2025`, `26-nanoserver-ltsc2025`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-
--	[`26-ea-19-jdk-nanoserver-ltsc2022`, `26-ea-19-nanoserver-ltsc2022`, `26-ea-jdk-nanoserver-ltsc2022`, `26-ea-nanoserver-ltsc2022`, `26-jdk-nanoserver-ltsc2022`, `26-nanoserver-ltsc2022`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/nanoserver-ltsc2022/Dockerfile)
-
 ## Shared Tags
 
 -	`26-ea-19-jdk`, `26-ea-19`, `26-ea-jdk`, `26-ea`, `26-jdk`, `26`:
 
 	-	[`26-ea-19-jdk-oraclelinux9`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/oraclelinux9/Dockerfile)
-	-	[`26-ea-19-jdk-windowsservercore-ltsc2025`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`26-ea-19-jdk-windowsservercore-ltsc2022`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`26-ea-19-jdk-windowsservercore`, `26-ea-19-windowsservercore`, `26-ea-jdk-windowsservercore`, `26-ea-windowsservercore`, `26-jdk-windowsservercore`, `26-windowsservercore`:
-
-	-	[`26-ea-19-jdk-windowsservercore-ltsc2025`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/windowsservercore-ltsc2025/Dockerfile)
-	-	[`26-ea-19-jdk-windowsservercore-ltsc2022`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/windowsservercore-ltsc2022/Dockerfile)
-
--	`26-ea-19-jdk-nanoserver`, `26-ea-19-nanoserver`, `26-ea-jdk-nanoserver`, `26-ea-nanoserver`, `26-jdk-nanoserver`, `26-nanoserver`:
-
-	-	[`26-ea-19-jdk-nanoserver-ltsc2025`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/nanoserver-ltsc2025/Dockerfile)
-	-	[`26-ea-19-jdk-nanoserver-ltsc2022`](https://github.com/docker-library/openjdk/blob/5f4ebde04e807b32991436ccdaa4b06e9b200875/26/jdk/windows/nanoserver-ltsc2022/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -116,7 +98,7 @@ Java is a registered trademark of Oracle and/or its affiliates.
 The most straightforward way to use this image is to use a Java container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project:
 
 ```dockerfile
-FROM openjdk:11
+FROM arm64v8/openjdk:11
 COPY . /usr/src/myapp
 WORKDIR /usr/src/myapp
 RUN javac Main.java
@@ -135,7 +117,7 @@ $ docker run -it --rm --name my-running-app my-java-app
 There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
 
 ```console
-$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp openjdk:11 javac Main.java
+$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/openjdk:11 javac Main.java
 ```
 
 This will add your current directory as a volume to the container, set the working directory to the volume, and run the command `javac Main.java` which will tell Java to compile the code in `Main.java` and output the Java class file to `Main.class`.
@@ -162,15 +144,15 @@ Some shells (notably, [the BusyBox `/bin/sh` included in Alpine Linux](https://g
 
 # Image Variants
 
-The `openjdk` images come in many flavors, each designed for a specific use case.
+The `arm64v8/openjdk` images come in many flavors, each designed for a specific use case.
 
-## `openjdk:<version>`
+## `arm64v8/openjdk:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
 Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `openjdk:<version>` (from 12 onwards), `openjdk:<version>-oracle` and `openjdk:<version>-oraclelinux8`
+## `arm64v8/openjdk:<version>` (from 12 onwards), `arm64v8/openjdk:<version>-oracle` and `arm64v8/openjdk:<version>-oraclelinux8`
 
 Starting with `openjdk:12` the default image as well as the `-oracle` and `-oraclelinux8` variants are based on the official [Oracle Linux 8 image](https://hub.docker.com/_/oraclelinux) which is provided under the GPLv2 as per the [Oracle Linux End User Agreement (EULA)](https://oss.oracle.com/ol8/EULA).
 
@@ -178,14 +160,6 @@ The `-oraclelinux7` variants are based on the official [Oracle Linux 7 image](ht
 
 The OpenJDK binaries are built by Oracle and are sourced from the [OpenJDK community](https://openjdk.java.net/). These binaries are licensed under the [GPLv2 with the Classpath Exception](https://openjdk.java.net/legal/gplv2+ce.html).
 
-## `openjdk:<version>-windowsservercore`
-
-This image is based on [Windows Server Core (`mcr.microsoft.com/windows/servercore`)](https://hub.docker.com/r/microsoft/windows-servercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
-
-For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
-
--	[Windows Containers Quick Start](https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce)
-
 # License
 
 View [license information](http://openjdk.java.net/legal/gplv2+ce.html) for the software contained in this image.

oraclelinux/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `oraclelinux` official image](https://hub.docker.com/_/oraclelinux) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,27 +26,27 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`10`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/10/Dockerfile)
+-	[`10`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/10/Dockerfile)
 
--	[`10-slim`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/10-slim/Dockerfile)
+-	[`10-slim`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/10-slim/Dockerfile)
 
--	[`9`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/9/Dockerfile)
+-	[`9`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/9/Dockerfile)
 
--	[`9-slim`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/9-slim/Dockerfile)
+-	[`9-slim`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/9-slim/Dockerfile)
 
--	[`9-slim-fips`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/9-slim-fips/Dockerfile)
+-	[`9-slim-fips`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/9-slim-fips/Dockerfile)
 
--	[`8.10`, `8`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/8/Dockerfile)
+-	[`8.10`, `8`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/8/Dockerfile)
 
--	[`8-slim`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/8-slim/Dockerfile)
+-	[`8-slim`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/8-slim/Dockerfile)
 
--	[`8-slim-fips`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/8-slim-fips/Dockerfile)
+-	[`8-slim-fips`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/8-slim-fips/Dockerfile)
 
--	[`7.9`, `7`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/7/Dockerfile)
+-	[`7.9`, `7`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/7/Dockerfile)
 
--	[`7-slim`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/7-slim/Dockerfile)
+-	[`7-slim`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/7-slim/Dockerfile)
 
--	[`7-slim-fips`](https://github.com/oracle/container-images/blob/fe3cfb9b6b7834daf2033b97256a4387b2c6dcf8/7-slim-fips/Dockerfile)
+-	[`7-slim-fips`](https://github.com/oracle/container-images/blob/c7f16b39d226cd22d073bf3e44fabe2f11637d75/7-slim-fips/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -75,7 +77,7 @@ Oracle Linux is an open-source operating system available under the GNU General
 
 ## How to use these images
 
-The Oracle Linux images are intended for use in the **FROM** field of a downstream `Dockerfile`. For example, to use the latest optimized Oracle Linux 8 image, specify `FROM oraclelinux:8`.
+The Oracle Linux images are intended for use in the **FROM** field of a downstream `Dockerfile`. For example, to use the latest optimized Oracle Linux 8 image, specify `FROM arm64v8/oraclelinux:8`.
 
 ## Removal of `latest` tag
 

orientdb/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `orientdb` official image](https://hub.docker.com/_/orientdb) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -28,10 +30,6 @@ WARNING:
 
 -	[`3.2.44-tp3`, `3.2-tp3`](https://github.com/orientechnologies/orientdb-docker/blob/0bb558c4efb3735b31003bd90fc094dc17b7ef5b/release/3.2.x/3.2.44-tp3/Dockerfile)
 
--	[`3.1.20`, `3.1`](https://github.com/orientechnologies/orientdb-docker/blob/a8a42acbe19dad60a051afe08ed625e66587dd37/release/3.1.x/3.1.20/Dockerfile)
-
--	[`3.1.20-tp3`, `3.1-tp3`](https://github.com/orientechnologies/orientdb-docker/blob/a8a42acbe19dad60a051afe08ed625e66587dd37/release/3.1.x/3.1.20-tp3/Dockerfile)
-
 # Quick reference (cont.)
 
 -	**Where to file issues**:  
@@ -62,7 +60,7 @@ WARNING:
 When OrientDB starts it asks for the root password. The root user is able to manage the OrientDB server: create new databases, manage users and roles. The root password can be passed to the container using an environment property:
 
 ```console
-$ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 -e ORIENTDB_ROOT_PASSWORD=rootpwd orientdb
+$ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 -e ORIENTDB_ROOT_PASSWORD=rootpwd arm64v8/orientdb
 ```
 
 The [Studio](http://orientdb.com/docs/last/Studio-Home-page.html) is accessible to http://<docker-host>:2480 (e.g.: http://localhost:2480)
@@ -79,7 +77,7 @@ $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
     -v <databases_path>:/orientdb/databases \
     -v <backup_path>:/orientdb/backup \
     -e ORIENTDB_ROOT_PASSWORD=rootpwd \
-    orientdb
+    arm64v8/orientdb
 ```
 
 **NOTE**: don't provide an **empty** config folder as volume, because OrientDB will startup with a very minimal configuration.
@@ -89,13 +87,13 @@ $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
 The OrientDB image contains a full fledge installation, so it is possible to run the [console](http://orientdb.com/docs/last/Console-Commands.html)
 
 ```console
-$ docker run --rm -it orientdb /orientdb/bin/console.sh
+$ docker run --rm -it arm64v8/orientdb /orientdb/bin/console.sh
 ```
 
 or even the etl
 
 ```console
-$ docker run  --rm -it -v <config_path>:/orientdb/config orientdb /orientdb/bin/oetl.sh ../config/oetl-config.json
+$ docker run  --rm -it -v <config_path>:/orientdb/config arm64v8/orientdb /orientdb/bin/oetl.sh ../config/oetl-config.json
 ```
 
 ### Override configuration parameters
@@ -109,7 +107,7 @@ $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
     -v <backup_path>:/orientdb/backup \
     -e ORIENTDB_ROOT_PASSWORD=rootpwd \
     -e ORIENTDB_NODE_NAME=odb1 \
-    orientdb /orientdb/bin/server.sh  -Ddistributed=true
+    arm64v8/orientdb /orientdb/bin/server.sh  -Ddistributed=true
 ```
 
 For further configuration options please refer to the [Configuration](http://orientdb.com/docs/last/Configuration.html) section of the online documentation.
@@ -121,7 +119,7 @@ Environment parameters such as heap size could be passed via command line:
 ```console
 $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
     -e ORIENTDB_ROOT_PASSWORD=rootpwd \
-    orientdb /orientdb/bin/server.sh -Xmx8g
+    arm64v8/orientdb /orientdb/bin/server.sh -Xmx8g
 ```
 
 # License

percona/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `percona` official image](https://hub.docker.com/_/percona) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,13 +26,7 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`8.0.43-34-centos`, `8.0-centos`, `8-centos`, `8.0.43-34`, `8.0`, `8`, `ps-8.0.43-34`, `ps-8.0`, `ps-8`](https://github.com/percona/percona-docker/blob/1a5a6f51cda0ad561e5afcbd9b1ec9e2dd3564d1/percona-server-8.0/Dockerfile-dockerhub)
-
--	[`psmdb-8.0.12`, `psmdb-8.0`](https://github.com/percona/percona-docker/blob/725e757d51b83f0a0a9c3b5242f6be02066e0a9b/percona-server-mongodb-8.0/Dockerfile-dockerhub)
-
--	[`psmdb-7.0.24`, `psmdb-7.0`](https://github.com/percona/percona-docker/blob/725e757d51b83f0a0a9c3b5242f6be02066e0a9b/percona-server-mongodb-7.0/Dockerfile-dockerhub)
-
--	[`psmdb-6.0.25`, `psmdb-6.0`](https://github.com/percona/percona-docker/blob/c37d7c35b5d3ddeacdf8b6c837e7735c14ace89b/percona-server-mongodb-6.0/Dockerfile-dockerhub)
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -65,30 +61,30 @@ It aims to retain close compatibility to the official MySQL releases, while focu
 
 # How to use this image
 
-## Start a `percona` server instance
+## Start a `arm64v8/percona` server instance
 
 Starting a Percona Server for MySQL instance is simple:
 
 ```console
-$ docker run --name some-percona -e MYSQL_ROOT_PASSWORD=my-secret-pw -d percona:tag
+$ docker run --name some-percona -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/percona:tag
 ```
 
 ... where `some-percona` is the name you want to assign to your container, `my-secret-pw` is the password to be set for the MySQL root user and `tag` is the tag specifying the MySQL version you want. See the list above for relevant tags.
 
 ## Connect to Percona Server from the MySQL command line client
 
-The following command starts another `percona` container instance and runs the `mysql` command line client against your original `percona` container, allowing you to execute SQL statements against your database instance:
+The following command starts another `arm64v8/percona` container instance and runs the `mysql` command line client against your original `arm64v8/percona` container, allowing you to execute SQL statements against your database instance:
 
 ```console
-$ docker run -it --network some-network --rm percona mysql -hsome-percona -uexample-user -p
+$ docker run -it --network some-network --rm arm64v8/percona mysql -hsome-percona -uexample-user -p
 ```
 
-... where `some-percona` is the name of your original `percona` container (connected to the `some-network` Docker network).
+... where `some-percona` is the name of your original `arm64v8/percona` container (connected to the `some-network` Docker network).
 
 This image can also be used as a client for non-Docker or remote instances:
 
 ```console
-$ docker run -it --rm percona mysql -hsome.mysql.host -usome-mysql-user -p
+$ docker run -it --rm arm64v8/percona mysql -hsome.mysql.host -usome-mysql-user -p
 ```
 
 More information about the MySQL command line client can be found in the [MySQL documentation](http://dev.mysql.com/doc/en/mysql.html)
@@ -119,7 +115,7 @@ Run `docker compose up`, wait for it to initialize completely, and visit `http:/
 
 ## Container shell access and viewing MySQL logs
 
-The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `percona` container:
+The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `arm64v8/percona` container:
 
 ```console
 $ docker exec -it some-percona bash
@@ -133,12 +129,12 @@ $ docker logs some-percona
 
 ## Using a custom MySQL configuration file
 
-The startup configuration is specified in the file `/etc/my.cnf`, and that file in turn includes any files found in the `/etc/my.cnf.d` directory that end with `.cnf`. Settings in files in this directory will augment and/or override settings in `/etc/my.cnf`. If you want to use a customized MySQL configuration, you can create your alternative configuration file in a directory on the host machine and then mount that directory location as `/etc/my.cnf.d` inside the `percona` container.
+The startup configuration is specified in the file `/etc/my.cnf`, and that file in turn includes any files found in the `/etc/my.cnf.d` directory that end with `.cnf`. Settings in files in this directory will augment and/or override settings in `/etc/my.cnf`. If you want to use a customized MySQL configuration, you can create your alternative configuration file in a directory on the host machine and then mount that directory location as `/etc/my.cnf.d` inside the `arm64v8/percona` container.
 
-If `/my/custom/config-file.cnf` is the path and name of your custom configuration file, you can start your `percona` container like this (note that only the directory path of the custom config file is used in this command):
+If `/my/custom/config-file.cnf` is the path and name of your custom configuration file, you can start your `arm64v8/percona` container like this (note that only the directory path of the custom config file is used in this command):
 
 ```console
-$ docker run --name some-percona -v /my/custom:/etc/my.cnf.d -e MYSQL_ROOT_PASSWORD=my-secret-pw -d percona:tag
+$ docker run --name some-percona -v /my/custom:/etc/my.cnf.d -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/percona:tag
 ```
 
 This will start a new container `some-percona` where the Percona Server for MySQL instance uses the combined startup settings from `/etc/my.cnf` and `/etc/my.cnf.d/config-file.cnf`, with settings from the latter taking precedence.
@@ -148,18 +144,18 @@ This will start a new container `some-percona` where the Percona Server for MySQ
 Many configuration options can be passed as flags to `mysqld`. This will give you the flexibility to customize the container without needing a `cnf` file. For example, if you want to change the default encoding and collation for all tables to use UTF-8 (`utf8mb4`) just run the following:
 
 ```console
-$ docker run --name some-percona -e MYSQL_ROOT_PASSWORD=my-secret-pw -d percona:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
+$ docker run --name some-percona -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/percona:tag --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
 ```
 
 If you would like to see a complete list of available options, just run:
 
 ```console
-$ docker run -it --rm percona:tag --verbose --help
+$ docker run -it --rm arm64v8/percona:tag --verbose --help
 ```
 
 ## Environment Variables
 
-When you start the `percona` image, you can adjust the configuration of the instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.
+When you start the `arm64v8/percona` image, you can adjust the configuration of the instance by passing one or more environment variables on the `docker run` command line. Do note that none of the variables below will have any effect if you start the container with a data directory that already contains a database: any pre-existing database will always be left untouched on container startup.
 
 ### `MYSQL_ROOT_PASSWORD`
 
@@ -208,7 +204,7 @@ Tuns on RocksDB Engine.
 As an alternative to passing sensitive information via environment variables, `_FILE` may be appended to the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in `/run/secrets/<secret_name>` files. For example:
 
 ```console
-$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql-root -d percona:tag
+$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql-root -d arm64v8/percona:tag
 ```
 
 Currently, this is only supported for `MYSQL_ROOT_PASSWORD`, `MYSQL_ROOT_HOST`, `MYSQL_DATABASE`, `MYSQL_USER`, and `MYSQL_PASSWORD`.
@@ -218,18 +214,18 @@ Currently, this is only supported for `MYSQL_ROOT_PASSWORD`, `MYSQL_ROOT_HOST`,
 Starting with Percona Server 8.0.35-27, telemetry will be enabled by default. If you decide not to send usage data to Percona, you can set the `PERCONA_TELEMETRY_DISABLE=1` environment variable. For example:
 
 ```console
-$ docker run --name some-mysql -e  PERCONA_TELEMETRY_DISABLE=1 -d percona:tag
+$ docker run --name some-mysql -e  PERCONA_TELEMETRY_DISABLE=1 -d arm64v8/percona:tag
 ```
 
 # Initializing a fresh instance
 
-When a container is started for the first time, a new database with the specified name will be created and initialized with the provided configuration variables. Furthermore, it will execute files with extensions `.sh`, `.sql` and `.sql.gz` that are found in `/docker-entrypoint-initdb.d`. Files will be executed in alphabetical order. You can easily populate your `percona` services by [mounting a SQL dump into that directory](https://docs.docker.com/storage/bind-mounts/) and provide [custom images](https://docs.docker.com/reference/dockerfile/) with contributed data. SQL files will be imported by default to the database specified by the `MYSQL_DATABASE` variable.
+When a container is started for the first time, a new database with the specified name will be created and initialized with the provided configuration variables. Furthermore, it will execute files with extensions `.sh`, `.sql` and `.sql.gz` that are found in `/docker-entrypoint-initdb.d`. Files will be executed in alphabetical order. You can easily populate your `arm64v8/percona` services by [mounting a SQL dump into that directory](https://docs.docker.com/storage/bind-mounts/) and provide [custom images](https://docs.docker.com/reference/dockerfile/) with contributed data. SQL files will be imported by default to the database specified by the `MYSQL_DATABASE` variable.
 
 # Caveats
 
 ## Where to Store Data
 
-Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `percona` images to familiarize themselves with the options available, including:
+Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `arm64v8/percona` images to familiarize themselves with the options available, including:
 
 -	Let Docker manage the storage of your database data [by writing the database files to disk on the host system using its own internal volume management](https://docs.docker.com/storage/volumes/). This is the default and is easy and fairly transparent to the user. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers.
 -	Create a data directory on the host system (outside the container) and [mount this to a directory visible from inside the container](https://docs.docker.com/storage/bind-mounts/). This places the database files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly.
@@ -237,10 +233,10 @@ Important note: There are several ways to store data used by applications that r
 The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:
 
 1.	Create a data directory on a suitable volume on your host system, e.g. `/my/own/datadir`.
-2.	Start your `percona` container like this:
+2.	Start your `arm64v8/percona` container like this:
 
 	```console
-	$ docker run --name some-percona -v /my/own/datadir:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d percona:tag
+	$ docker run --name some-percona -v /my/own/datadir:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d arm64v8/percona:tag
 	```
 
 The `-v /my/own/datadir:/var/lib/mysql` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/mysql` inside the container, where MySQL by default will write its data files.
@@ -253,7 +249,7 @@ If the application you're trying to connect to MySQL does not handle MySQL downt
 
 ## Usage against an existing database
 
-If you start your `percona` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), the `$MYSQL_ROOT_PASSWORD` variable should be omitted from the run command line; it will in any case be ignored, and the pre-existing database will not be changed in any way.
+If you start your `arm64v8/percona` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), the `$MYSQL_ROOT_PASSWORD` variable should be omitted from the run command line; it will in any case be ignored, and the pre-existing database will not be changed in any way.
 
 ## Creating database dumps
 

perl/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `perl` official image](https://hub.docker.com/_/perl) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -152,7 +154,7 @@ Perl is a high-level, general-purpose, interpreted, dynamic programming language
 ## Create a `Dockerfile` in your Perl app project
 
 ```dockerfile
-FROM perl:5.34
+FROM arm64v8/perl:5.34
 COPY . /usr/src/myapp
 WORKDIR /usr/src/myapp
 CMD [ "perl", "./your-daemon-or-script.pl" ]
@@ -170,7 +172,7 @@ $ docker run -it --rm --name my-running-app my-perl-app
 For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Perl script by using the Perl Docker image directly:
 
 ```console
-$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp perl:5.34 perl your-daemon-or-script.pl
+$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/perl:5.34 perl your-daemon-or-script.pl
 ```
 
 ## Coexisting with Debian's `/usr/bin/perl`
@@ -186,7 +188,7 @@ See also [Perl/docker-perl#26](https://github.com/Perl/docker-perl/issues/26) fo
 As Perl will run as PID 1 by default in containers (unless an [ENTRYPOINT](https://docs.docker.com/reference/dockerfile/#entrypoint) is set,) special care needs to be considered when expecting to send signals (particularly SIGINT or SIGTERM) to it. For example, running
 
 ```console
-$ docker run -it --name sleeping_beauty --rm perl:5.34 perl -E 'sleep 300'
+$ docker run -it --name sleeping_beauty --rm arm64v8/perl:5.34 perl -E 'sleep 300'
 ```
 
 and doing on another terminal,
@@ -198,7 +200,7 @@ $ docker exec sleeping_beauty kill 1
 will *not* stop the perl running on the `sleeping_beauty` container (it will keep running until the `sleep 300` finishes.) To do so, one must set a signal handler like this:
 
 ```console
-$ docker run -it --name quick_nap --rm perl:5.34 perl -E '$SIG{TERM} = sub { $sig++; say "recv TERM" }; sleep 300; say "waking up" if $sig'
+$ docker run -it --name quick_nap --rm arm64v8/perl:5.34 perl -E '$SIG{TERM} = sub { $sig++; say "recv TERM" }; sleep 300; say "waking up" if $sig'
 ```
 
 so doing `docker exec quick_nap kill 1` (or the simpler `docker stop quick_nap`) will immediately stop the container, and print `recv TERM` in the other terminal. Note that the signal handler does not stop the perl process itself unless it calls a `die` or `exit`; in this case, perl will continue and print `waking up` *after* it receives the signal.
@@ -215,10 +217,10 @@ See also [Perl/docker-perl#140](https://github.com/Perl/docker-perl/issues/140)
 
 ## Example: Creating a reusable Carton image for Perl projects
 
-Suppose you have a project that uses [Carton](https://metacpan.org/pod/Carton) to manage Perl dependencies. You can create a `perl:carton` image that makes use of the [ONBUILD](https://docs.docker.com/reference/dockerfile/#onbuild) instruction in its `Dockerfile`, like this:
+Suppose you have a project that uses [Carton](https://metacpan.org/pod/Carton) to manage Perl dependencies. You can create a `arm64v8/perl:carton` image that makes use of the [ONBUILD](https://docs.docker.com/reference/dockerfile/#onbuild) instruction in its `Dockerfile`, like this:
 
 ```dockerfile
-FROM perl:5.34
+FROM arm64v8/perl:5.34
 
 RUN cpanm Carton \
     && mkdir -p /usr/src/app
@@ -230,18 +232,18 @@ ONBUILD RUN carton install
 ONBUILD COPY . /usr/src/app
 ```
 
-Then, in your Carton project, you can now reduce your project's `Dockerfile` into a single line of `FROM perl:carton`, which may be enough to build a stand-alone image.
+Then, in your Carton project, you can now reduce your project's `Dockerfile` into a single line of `FROM arm64v8/perl:carton`, which may be enough to build a stand-alone image.
 
-Having a single `perl:carton` base image is useful especially if you have multiple Carton-based projects in development, to avoid "boilerplate" coding of installing Carton and/or copying the project source files into the derived image. Keep in mind, though, about certain things to consider when using the Perl image in this way:
+Having a single `arm64v8/perl:carton` base image is useful especially if you have multiple Carton-based projects in development, to avoid "boilerplate" coding of installing Carton and/or copying the project source files into the derived image. Keep in mind, though, about certain things to consider when using the Perl image in this way:
 
 -	This kind of base image will hide the useful bits (such as the`COPY`/`RUN` above) in the image, separating it from more specific Dockerfiles using the base image. This might lead to confusion when creating further derived images, so be aware of how [ONBUILD triggers](https://docs.docker.com/reference/dockerfile/#onbuild) work and plan appropriately.
 -	There is the cost of maintaining an extra base image build, so if you're working on a single Carton project and/or plan to publish it, then it may be more preferable to derive directly from a versioned `perl` image instead.
 
 # Image Variants
 
-The `perl` images come in many flavors, each designed for a specific use case.
+The `arm64v8/perl` images come in many flavors, each designed for a specific use case.
 
-## `perl:<version>`
+## `arm64v8/perl:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
@@ -249,9 +251,9 @@ Some of these tags may have names like bookworm, bullseye, or trixie in them. Th
 
 This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system.
 
-## `perl:<version>-slim`
+## `arm64v8/perl:<version>-slim`
 
-This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `perl`. Unless you are working in an environment where *only* the `perl` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
+This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run `arm64v8/perl`. Unless you are working in an environment where *only* the `arm64v8/perl` image will be deployed and you have space constraints, we highly recommend using the default image of this repository.
 
 # License
 

photon/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `photon` official image](https://hub.docker.com/_/photon) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -24,11 +26,11 @@ WARNING:
 
 # Supported tags and respective `Dockerfile` links
 
--	[`5.0`, `5.0-20251011`, `latest`](https://github.com/vmware/photon-docker-image/blob/8921fff02b3b2ce4bbc6116b4c6b4c708562aa96/docker/Dockerfile)
+-	[`5.0`, `5.0-20251011`, `latest`](https://github.com/vmware/photon-docker-image/blob/eafb1cc548b25fdb1e4061dcfa1027b5d0e45e4a/docker/Dockerfile)
 
--	[`4.0`, `4.0-20251012`](https://github.com/vmware/photon-docker-image/blob/75d6173bc370ace82b24de6e7319483fd8e54869/docker/Dockerfile)
+-	[`4.0`, `4.0-20251012`](https://github.com/vmware/photon-docker-image/blob/81e7d951ccf2cc78baf3adc4df775b3ff1a34e28/docker/Dockerfile)
 
--	[`3.0`, `3.0-20250316`](https://github.com/vmware/photon-docker-image/blob/f848d5df815c0afe76b42a608d49df0e87af51c2/docker/Dockerfile)
+-	[`3.0`, `3.0-20250316`](https://github.com/vmware/photon-docker-image/blob/93a0c62b9b7790fc27d1413f65073ef1a2894bab/docker/Dockerfile)
 
 # Quick reference (cont.)
 
@@ -61,7 +63,7 @@ See the [FAQ](http://vmware.github.io/photon/assets/files/photon_faqs.pdf) for m
 
 ## How to use these images
 
-Photon OS images are intended for use in the **FROM** field of an application's `Dockerfile`. For example, to use VMware Photon 1.0GA as the base of an image, specify `FROM photon:1.0GA`.
+Photon OS images are intended for use in the **FROM** field of an application's `Dockerfile`. For example, to use VMware Photon 1.0GA as the base of an image, specify `FROM arm64v8/photon:1.0GA`.
 
 ## Support
 

php-zendserver/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `php-zendserver` official image](https://hub.docker.com/_/php-zendserver) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # **DEPRECATION NOTICE**
 
 This image is not actively maintained (and [has not been for years](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fphp-zendserver)). It is highly recommended for users to seek out alternatives.
@@ -28,7 +30,7 @@ This image is not actively maintained (and [has not been for years](https://gith
 
 # Supported tags and respective `Dockerfile` links
 
-**No supported tags**
+**WARNING:** THIS IMAGE *IS NOT SUPPORTED* ON THE `arm64v8` ARCHITECTURE
 
 # Quick reference (cont.)
 
@@ -84,12 +86,12 @@ Zend Server is shared on [Docker-Hub] as **php-zendserver**.
 
 To start a single Zend Server instance, execute:
 
-	    $ docker run php-zendserver
+	    $ docker run arm64v8/php-zendserver
 
 -	You can specify the PHP and Zend Server version by adding ':<php-version>' or ':&lt;ZS-version&gt;-php&lt;version&gt;' to the 'docker run' command.
 
 		for example: 
-		$docker run php-zendserver:8.5-php5.6
+		$docker run arm64v8/php-zendserver:8.5-php5.6
 
 #### Availible versions:
 
@@ -101,11 +103,11 @@ To start a single Zend Server instance, execute:
 
 To start a Zend Server cluster, execute the following command for each cluster node:
 
-	    $ docker run -e MYSQL_HOSTNAME=<db-ip> -e MYSQL_PORT=3306 -e MYSQL_USERNAME=<username> -e MYSQL_PASSWORD=<password> -e MYSQL_DBNAME=zend php-zendserver
+	    $ docker run -e MYSQL_HOSTNAME=<db-ip> -e MYSQL_PORT=3306 -e MYSQL_USERNAME=<username> -e MYSQL_PASSWORD=<password> -e MYSQL_DBNAME=zend arm64v8/php-zendserver
 
 #### Bring your own license
 
-To use your own Zend Server license: $ docker run php-zendserver -e ZEND_LICENSE_KEY=<license-key> -e ZEND_LICENSE_ORDER=<order-number>
+To use your own Zend Server license: $ docker run arm64v8/php-zendserver -e ZEND_LICENSE_KEY=<license-key> -e ZEND_LICENSE_ORDER=<order-number>
 
 #### Launching the Container from Dockerfile
 
@@ -133,7 +135,7 @@ Once started, the container will output the information required to access the P
 
 To access the container **remotely**, port forwarding must be configured, either manually or using docker. For example, this command redirects port 80 to port 88, and port 10081 (Zend Server UI port) to port 10088:
 
-	    $ docker run -p 88:80 -p 10088:10081 php-zendserver
+	    $ docker run -p 88:80 -p 10088:10081 arm64v8/php-zendserver
 
 ##### For clustered instances:
 

php/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `php` official image](https://hub.docker.com/_/php) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -252,7 +254,7 @@ PHP is a server-side scripting language designed for web development, but which
 ### Create a `Dockerfile` in your PHP project
 
 ```dockerfile
-FROM php:8.2-cli
+FROM arm64v8/php:8.2-cli
 COPY . /usr/src/myapp
 WORKDIR /usr/src/myapp
 CMD [ "php", "./your-script.php" ]
@@ -270,7 +272,7 @@ $ docker run -it --rm --name my-running-app my-php-app
 For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a PHP script by using the PHP Docker image directly:
 
 ```console
-$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp php:8.2-cli php your-script.php
+$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp arm64v8/php:8.2-cli php your-script.php
 ```
 
 ## How to install more PHP extensions
@@ -282,7 +284,7 @@ We provide the helper scripts `docker-php-ext-configure`, `docker-php-ext-instal
 In order to keep the images smaller, PHP's source is kept in a compressed tar file. To facilitate linking of PHP's source with any extension, we also provide the helper script `docker-php-source` to easily extract the tar or delete the extracted source. Note: if you do use `docker-php-source` to extract the source, be sure to delete it in the same layer of the docker image.
 
 ```Dockerfile
-FROM php:8.2-cli
+FROM arm64v8/php:8.2-cli
 RUN docker-php-source extract \
 	# do important things \
 	&& docker-php-source delete
@@ -293,7 +295,7 @@ RUN docker-php-source extract \
 For example, if you want to have a PHP-FPM image with the `gd` extension, you can inherit the base image that you like, and write your own `Dockerfile` like this:
 
 ```dockerfile
-FROM php:8.2-fpm
+FROM arm64v8/php:8.2-fpm
 RUN apt-get update && apt-get install -y \
 		libfreetype-dev \
 		libjpeg62-turbo-dev \
@@ -317,14 +319,14 @@ Some extensions are compiled by default. This depends on the PHP version you are
 Some extensions are not provided with the PHP source, but are instead available through [PECL](https://pecl.php.net/). To install a PECL extension, use `pecl install` to download and compile it, then use `docker-php-ext-enable` to enable it:
 
 ```dockerfile
-FROM php:8.2-cli
+FROM arm64v8/php:8.2-cli
 RUN pecl install redis-5.3.7 \
 	&& pecl install xdebug-3.2.1 \
 	&& docker-php-ext-enable redis xdebug
 ```
 
 ```dockerfile
-FROM php:8.2-cli
+FROM arm64v8/php:8.2-cli
 RUN apt-get update && apt-get install -y libmemcached-dev libssl-dev zlib1g-dev \
 	&& pecl install memcached-3.2.0 \
 	&& docker-php-ext-enable memcached
@@ -339,7 +341,7 @@ Unlike PHP core extensions, PECL extensions should be installed in series to fai
 Some extensions are not provided via either Core or PECL; these can be installed too, although the process is less automated:
 
 ```dockerfile
-FROM php:8.2-cli
+FROM arm64v8/php:8.2-cli
 RUN curl -fsSL '[url-to-custom-php-module]' -o module-name.tar.gz \
 	&& mkdir -p module-name \
 	&& sha256sum -c "[shasum-value]  module-name.tar.gz" \
@@ -359,7 +361,7 @@ RUN curl -fsSL '[url-to-custom-php-module]' -o module-name.tar.gz \
 The `docker-php-ext-*` scripts *can* accept an arbitrary path, but it must be absolute (to disambiguate from built-in extension names), so the above example could also be written as the following:
 
 ```dockerfile
-FROM php:8.2-cli
+FROM arm64v8/php:8.2-cli
 RUN curl -fsSL '[url-to-custom-php-module]' -o module-name.tar.gz \
 	&& mkdir -p /tmp/module-name \
 	&& sha256sum -c "[shasum-value]  module-name.tar.gz" \
@@ -402,7 +404,7 @@ The default config can be customized by copying configuration files into the `$P
 ### Example
 
 ```dockerfile
-FROM php:8.2-fpm-alpine
+FROM arm64v8/php:8.2-fpm-alpine
 
 # Use the default production configuration
 RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"
@@ -412,26 +414,26 @@ In many production environments, it is also recommended to (build and) enable th
 
 # Image Variants
 
-The `php` images come in many flavors, each designed for a specific use case.
+The `arm64v8/php` images come in many flavors, each designed for a specific use case.
 
 Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.
 
-## `php:<version>-cli`
+## `arm64v8/php:<version>-cli`
 
 This variant contains the [PHP CLI](https://secure.php.net/manual/en/features.commandline.php) tool with default mods. If you need a web server, this is probably not the image you are looking for. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as a base from which to build other images.
 
 It also is the only variant which contains the (not recommended) `php-cgi` binary, which is likely necessary for some things like [PPM](https://github.com/php-pm/php-pm).
 
-Note that *all* variants of `php` contain the PHP CLI (`/usr/local/bin/php`).
+Note that *all* variants of `arm64v8/php` contain the PHP CLI (`/usr/local/bin/php`).
 
-## `php:<version>-apache`
+## `arm64v8/php:<version>-apache`
 
 This image contains Debian's Apache httpd in conjunction with PHP (as `mod_php`) and uses `mpm_prefork` by default.
 
 ### Apache with a `Dockerfile`
 
 ```dockerfile
-FROM php:7.2-apache
+FROM arm64v8/php:7.2-apache
 COPY src/ /var/www/html/
 ```
 
@@ -447,7 +449,7 @@ We recommend that you add a `php.ini` configuration file; see the "Configuration
 ### Apache without a `Dockerfile`
 
 ```console
-$ docker run -d -p 80:80 --name my-apache-php-app -v "$PWD":/var/www/html php:7.2-apache
+$ docker run -d -p 80:80 --name my-apache-php-app -v "$PWD":/var/www/html arm64v8/php:7.2-apache
 ```
 
 ### Changing `DocumentRoot` (or other Apache configuration)
@@ -455,7 +457,7 @@ $ docker run -d -p 80:80 --name my-apache-php-app -v "$PWD":/var/www/html php:7.
 Some applications may wish to change the default `DocumentRoot` in Apache (away from `/var/www/html`). The following demonstrates one way to do so using an environment variable (which can then be modified at container runtime as well):
 
 ```dockerfile
-FROM php:7.1-apache
+FROM arm64v8/php:7.1-apache
 
 ENV APACHE_DOCUMENT_ROOT /path/to/new/root
 
@@ -465,7 +467,7 @@ RUN sed -ri -e 's!/var/www/!${APACHE_DOCUMENT_ROOT}!g' /etc/apache2/apache2.conf
 
 A similar technique could be employed for other Apache configuration options.
 
-## `php:<version>-fpm`
+## `arm64v8/php:<version>-fpm`
 
 This variant contains [PHP's FastCGI Process Manager (FPM)](https://www.php.net/fpm), which is the recommended FastCGI implementation for PHP.
 
@@ -481,7 +483,7 @@ Some potentially helpful resources:
 
 **WARNING:** the FastCGI protocol is inherently trusting, and thus *extremely* insecure to expose outside of a private container network -- unless you know *exactly* what you are doing (and are willing to accept the extreme risk), do not use Docker's `--publish` (`-p`) flag with this image variant.
 
-## `php:<version>-alpine`
+## `arm64v8/php:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
 

phpmyadmin/README.md

@@ -14,6 +14,8 @@ WARNING:
 
 -->
 
+**Note:** this is the "per-architecture" repository for the `arm64v8` builds of [the `phpmyadmin` official image](https://hub.docker.com/_/phpmyadmin) -- for more information, see ["Architectures other than amd64?" in the official images documentation](https://github.com/docker-library/official-images#architectures-other-than-amd64) and ["An image's source changed in Git, now what?" in the official images FAQ](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
+
 # Quick reference
 
 -	**Maintained by**:  
@@ -94,7 +96,7 @@ We provide three variations:
 First you need to run a MySQL or MariaDB server in Docker, and the phpMyAdmin image needs to be linked to the running database container:
 
 ```sh
-docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin
+docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 arm64v8/phpmyadmin
 ```
 
 ## Usage with external server
@@ -102,7 +104,7 @@ docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 phpmyadmin
 You can specify a MySQL host in the `PMA_HOST` environment variable. You can also use `PMA_PORT` to specify the port of the server in case it's not the default one:
 
 ```sh
-docker run --name phpmyadmin -d -e PMA_HOST=dbhost -p 8080:80 phpmyadmin
+docker run --name phpmyadmin -d -e PMA_HOST=dbhost -p 8080:80 arm64v8/phpmyadmin
 ```
 
 ## Usage with arbitrary server
@@ -110,7 +112,7 @@ docker run --name phpmyadmin -d -e PMA_HOST=dbhost -p 8080:80 phpmyadmin
 You can use arbitrary servers by adding the environment variable `PMA_ARBITRARY=1` to the startup command:
 
 ```sh
-docker run --name phpmyadmin -d -e PMA_ARBITRARY=1 -p 8080:80 phpmyadmin
+docker run --name phpmyadmin -d -e PMA_ARBITRARY=1 -p 8080:80 arm64v8/phpmyadmin
 ```
 
 ## Usage with `docker compose` and an arbitrary server
@@ -149,7 +151,7 @@ You can add your own custom config.inc.php settings (such as Configuration Stora
 On the `docker run` line like this:
 
 ```sh
-docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php phpmyadmin
+docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/config.user.inc.php:/etc/phpmyadmin/config.user.inc.php arm64v8/phpmyadmin
 ```
 
 Be sure to have `<?php` as your first line of the configuration file or the contents will not be detected as PHP code.
@@ -174,7 +176,7 @@ you can also consider storing your custom configuration files in the folder `/et
 On the `docker run` line like this:
 
 ```sh
-docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/conf.d:/etc/phpmyadmin/conf.d:ro phpmyadmin
+docker run --name phpmyadmin -d --link mysql_db_server:db -p 8080:80 -v /some/local/directory/conf.d:/etc/phpmyadmin/conf.d:ro arm64v8/phpmyadmin
 ```
 
 ## Usage behind a reverse proxy
@@ -194,11 +196,11 @@ In order to keep your sessions active between container updates you will need to
 Set the variable `PMA_SSL` to `1` to enable SSL usage from phpMyAdmin to the MySQL server. The default value is `0`. The variable `PMA_SSLS` can be used as a comma seperated sequence of `0` and `1` where multiple hosts are mentioned. Values order must follow the `PMA_HOSTS` and will be computed accordingly.
 
 ```sh
-docker run --name phpmyadmin -d -e PMA_HOSTS=sslhost -e PMA_SSL=1 -p 8080:80 phpmyadmin
+docker run --name phpmyadmin -d -e PMA_HOSTS=sslhost -e PMA_SSL=1 -p 8080:80 arm64v8/phpmyadmin
 ```
 
 ```sh
-docker run --name phpmyadmin -d -e PMA_HOSTS='sslhost,nosslhost' -e PMA_SSLS='1,0' -p 8080:80 phpmyadmin
+docker run --name phpmyadmin -d -e PMA_HOSTS='sslhost,nosslhost' -e PMA_SSLS='1,0' -p 8080:80 arm64v8/phpmyadmin
 ```
 
 ## Environment variables summary
@@ -246,7 +248,7 @@ docker run --name phpmyadmin -d -e PMA_HOSTS='sslhost,nosslhost' -e PMA_SSLS='1,
 For usage with Docker secrets, appending `_FILE` to the `PMA_PASSWORD` environment variable is allowed (it overrides `PMA_PASSWORD` if it is set):
 
 ```sh
-docker run --name phpmyadmin -d -e PMA_PASSWORD_FILE=/run/secrets/db_password.txt -p 8080:80 phpmyadmin
+docker run --name phpmyadmin -d -e PMA_PASSWORD_FILE=/run/secrets/db_password.txt -p 8080:80 arm64v8/phpmyadmin
 ```
 
 #### Variables that can store the file contents using `_BASE64`
@@ -282,13 +284,13 @@ Please report any issues with phpMyAdmin to https://github.com/phpmyadmin/phpmya
 
 # Image Variants
 
-The `phpmyadmin` images come in many flavors, each designed for a specific use case.
+The `arm64v8/phpmyadmin` images come in many flavors, each designed for a specific use case.
 
-## `phpmyadmin:<version>`
+## `arm64v8/phpmyadmin:<version>`
 
 This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
 
-## `phpmyadmin:<version>-alpine`
+## `arm64v8/phpmyadmin:<version>-alpine`
 
 This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.