xin053/builder repository overview

⁠mirror_docker_image

github⁠

中文文档⁠

Synchronize the docker image from one registry to another through github action. For example, synchronize the specified docker image under gcr.io to docker.io.

⁠Usage

Open a new issue, then use the image name to be synchronized as title (The image name needs to be a full name, which means registry and tag cannot be omitted), the content of issue can be empty.

For example: open a new issue with title k8s.gcr.io/kube-state-metrics/kube-state-metrics:latest, Then the github action will automatically pull the image and push it to the xin053 repository⁠, then you can use docker pull xin053/kube-state-metrics:latest command to pull the image.

You can view the synchronized docker images through the link below:

https://hub.docker.com/u/xin053⁠

⁠Customize action

After fork this repository, check issues in features on the Settings page of the forked repository, then enable GitHub actions on the Actions page, add corresponding secrets as needed, then you can create issue in your forked repository to synchronize the docker image

⁠secrets supported by action

⁠If the source registry needs to log in

After fork this github repository, add the following secrets:

Remarks: If you log in with token on docker hub, you cannot modify the description of the synchronized docker images

For details: https://github.com/peter-evans/dockerhub-description/issues/10⁠

⁠If the target registry is not docker.io

After fork this github repository, add the following secrets:

⁠Project stats