Docker push fails in GitHub Actions due to incorrect registry hostname for Artifact Registry

Below is a list of items to double-check and update in your workflow and manual commands:

1. Use the Correct Registry Hostname

The DNS error

  “Get "https://us-east1-docker-pkg.dev/v2/": dial tcp: lookup us-east1-docker-pkg.dev on 127.0.0.53:53: no such host”

suggests that the registry hostname is not correct. When using Artifact Registry, the correct hostname format is:

  REGION-docker.pkg.dev

In your workflow you were using “us-east1-docker-pkg.dev” (with a hyphen instead of a period before “pkg”), while the proper domain should be “us-east1-docker.pkg.dev”. For example:

YAMLCopied
gcloud auth configure-docker us-east1-docker.pkg.dev
docker build -t us-east1-docker.pkg.dev/${{ env.PROJECT_ID }}/astra-frontend/node:20.18.2 ./astra-frontend
docker push us-east1-docker.pkg.dev/${{ env.PROJECT_ID }}/astra-frontend/node:20.18.2

Make sure to update the region if your Artifact Registry repository is in a different region.

2. Ensure the Artifact Registry Repository Exists

Double-check that you have created the Artifact Registry repository in the correct region using a command like:

BASHCopied
gcloud artifacts repositories create REPOSITORY \
  --repository-format=docker \
  --location=us-east1

Replace REPOSITORY with your repository name. The repository location in your commands and the workflow should match.

3. Validate Service Account Permissions

The authentication error from manual pushes:

  “denied: Unauthenticated request. Unauthenticated requests do not have permission "artifactregistry.repositories.uploadArtifacts" …”

indicates a permissions issue. Verify that:

• The Artifact Registry API is enabled.
• The service account used (or the one impersonated) has the necessary permissions (e.g., Artifact Registry Administrator or Artifact Registry Writer).
• If you are using Workload Identity, confirm that the service account is properly bound to the Workload Identity Pool.

4. Review Authentication Steps in GitHub Actions

Your workflow uses the official actions for authentication and gcloud setup. Once you fix the registry hostname, the authentication steps should work as expected. For instance, you are already using:

YAMLCopied
- id: 'auth'
  uses: 'google-github-actions/auth@v2'
  with:
    workload_identity_provider: ${{ secrets.WORKLOAD_IDENTITY_PROVIDER }}
    service_account: ${{ secrets.SERVICE_ACCOUNT_EMAIL }}

Ensure that the secrets provided are valid, and that the service account has been granted the required permissions to perform Artifact Registry pushes.

Summary

The primary issue appears to be an incorrect registry URL. Correct your hostname formatting from “us-east1-docker-pkg.dev” to “us-east1-docker.pkg.dev” in all relevant places (gcloud auth configuration, docker build, and push commands). Then verify that your repository exists in that region and that your service account has the proper permissions.

Making these updates should resolve both the DNS lookup issue in your CI/CD workflow and the authentication error when pushing manually.