Skip to content

Commit ed12e66

Browse files
authored
Merge pull request #37566 from github/repo-sync
Repo sync
2 parents d5bd8c1 + 4e253f1 commit ed12e66

File tree

3 files changed

+5
-0
lines changed

3 files changed

+5
-0
lines changed

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

+2
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ In this guide, we will use the Docker `build-push-action` action to build the Do
5050

5151
## Publishing images to Docker Hub
5252

53+
{% data reusables.actions.jobs.dockerhub-ratelimit-ghr %}
54+
5355
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.
5456

5557
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.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
> [!NOTE]
2+
> 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.
Original file line numberDiff line numberDiff line change
@@ -1 +1,2 @@
11
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.
2+
{% data reusables.actions.jobs.dockerhub-ratelimit-ghr %}

0 commit comments

Comments
 (0)