You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue with Pushing Docker Images to Self-Hosted Registry via docker/build-push-action@v6 on Self-Hosted GitHub Actions Runner Behind Reverse Proxy
#3717
I'm using a self-hosted GitHub Actions runner setup with Actions Runner Controller (ARC) on Azure AKS, along with a small VM serving as a proxy for the AKS. My self-hosted Docker registry is set up with a Nginx reverse proxy and is configured to only accept requests from the VM proxy server from azure. I'm experiencing issues when trying to push Docker images to the registry using docker/build-push-action@v6 in GitHub Actions. The push works flawlessly when I build and push the Docker images using regular Docker commands in the pipeline script, but it fails with a 403 Forbidden error response when using the GitHub Action. I suspect this is because the docker/build-push-action@v6 GitHub Action is not utilizing the proxy VM configured for the AKS cluster.
I also tried to include the proxy's on builds-args but its still not working.
What could be causing this discrepancy, and how can I resolve it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm using a self-hosted GitHub Actions runner setup with Actions Runner Controller (ARC) on Azure AKS, along with a small VM serving as a proxy for the AKS. My self-hosted Docker registry is set up with a Nginx reverse proxy and is configured to only accept requests from the VM proxy server from azure. I'm experiencing issues when trying to push Docker images to the registry using docker/build-push-action@v6 in GitHub Actions. The push works flawlessly when I build and push the Docker images using regular Docker commands in the pipeline script, but it fails with a 403 Forbidden error response when using the GitHub Action. I suspect this is because the docker/build-push-action@v6 GitHub Action is not utilizing the proxy VM configured for the AKS cluster.
I also tried to include the proxy's on builds-args but its still not working.
What could be causing this discrepancy, and how can I resolve it?
Beta Was this translation helpful? Give feedback.
All reactions