mirror of
				https://github.com/docker/login-action.git
				synced 2025-10-31 01:40:11 +08:00 
			
		
		
		
	Add example for Google Artifact Registry
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
This commit is contained in:
		
							parent
							
								
									39ef12fb7a
								
							
						
					
					
						commit
						3b9e1f51cd
					
				
							
								
								
									
										36
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										36
									
								
								README.md
									
									
									
									
									
								
							| @ -24,6 +24,7 @@ ___ | ||||
|   * [GitLab](#gitlab) | ||||
|   * [Azure Container Registry (ACR)](#azure-container-registry-acr) | ||||
|   * [Google Container Registry (GCR)](#google-container-registry-gcr) | ||||
|   * [Google Artifact Registry (GAR)](#google-artifact-registry-gar) | ||||
|   * [AWS Elastic Container Registry (ECR)](#aws-elastic-container-registry-ecr) | ||||
| * [Customizing](#customizing) | ||||
|   * [inputs](#inputs) | ||||
| @ -162,6 +163,11 @@ jobs: | ||||
| 
 | ||||
| ### Google Container Registry (GCR) | ||||
| 
 | ||||
| > [Google Artifact Registry](#google-artifact-registry-gar) is the evolution of Google Container Registry. As a | ||||
| > fully-managed service with support for both container images and non-container artifacts. If you currently use | ||||
| > Google Container Registry, use the information [on this page](https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr) | ||||
| > to learn about transitioning to Google Artifact Registry.  | ||||
| 
 | ||||
| Use a service account with the ability to push to GCR and [configure access control](https://cloud.google.com/container-registry/docs/access-control). | ||||
| Then create and download the JSON key for this service account and save content of `.json` file | ||||
| [as a secret](https://docs.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) | ||||
| @ -187,6 +193,36 @@ jobs: | ||||
|           password: ${{ secrets.GCR_JSON_KEY }} | ||||
| ``` | ||||
| 
 | ||||
| ### Google Artifact Registry (GAR) | ||||
| 
 | ||||
| Use a service account with the ability to push to GAR and [configure access control](https://cloud.google.com/artifact-registry/docs/access-control). | ||||
| Then create and download the JSON key for this service account and save content of `.json` file | ||||
| [as a secret](https://docs.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) | ||||
| called `GAR_JSON_KEY` in your GitHub repo. Ensure you set the username to `_json_key`. | ||||
| 
 | ||||
| ```yaml | ||||
| name: ci | ||||
| 
 | ||||
| on: | ||||
|   push: | ||||
|     branches: master | ||||
| 
 | ||||
| jobs: | ||||
|   login: | ||||
|     runs-on: ubuntu-latest | ||||
|     steps: | ||||
|       - | ||||
|         name: Login to GAR | ||||
|         uses: docker/login-action@v1 | ||||
|         with: | ||||
|           registry: <location>-docker.pkg.dev | ||||
|           username: _json_key | ||||
|           password: ${{ secrets.GAR_JSON_KEY }} | ||||
| ``` | ||||
| 
 | ||||
| > Replace `<location>` with the regional or multi-regional [location](https://cloud.google.com/artifact-registry/docs/repo-organize#locations) | ||||
| > of the repository where the image is stored. | ||||
| 
 | ||||
| ### AWS Elastic Container Registry (ECR) | ||||
| 
 | ||||
| Use an IAM user with the [ability to push to ECR](https://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr_managed_policies.html). | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user
	 CrazyMax
						CrazyMax