Adding a note about DockerHub limits not applying for GHRs (#55132)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>

Author: 3 people

content/actions/use-cases-and-examples/publishing-packages/publishing-docker-images.md

@@ -50,6 +50,8 @@ In this guide, we will use the Docker `build-push-action` action to build the Do
 
 ## Publishing images to Docker Hub
 
+{% data reusables.actions.jobs.dockerhub-ratelimit-ghr %}
+
 Each time you create a new release on {% data variables.product.github %}, you can trigger a workflow to publish your image. The workflow in the example below runs when the `release` event triggers with the `published` activity type.
 
 In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.

data/reusables/actions/jobs/dockerhub-ratelimit-ghr.md

@@ -0,0 +1,2 @@
+> [!NOTE]
+> Docker Hub normally imposes rate limits on both push and pull operations which will affect jobs on self-hosted runners. However, {% data variables.product.github %}-hosted runners are not subject to these limits based on an agreement between {% data variables.product.github %} and Docker.

data/reusables/actions/jobs/section-running-jobs-in-a-container-image.md

@@ -1 +1,2 @@
 Use `jobs.<job_id>.container.image` to define the Docker image to use as the container to run the action. The value can be the Docker Hub image name or a registry name.
+{% data reusables.actions.jobs.dockerhub-ratelimit-ghr %}