Fix Docker Hub rate limiting with authentication #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add Docker Hub login step to all container-based jobs - Use docker/login-action@v3 with secrets for authentication - Set continue-on-error: true for graceful fallback - Resolves 'unauthorized: authentication required' errors This addresses Docker Hub's stricter rate limiting policies in 2024 that affect GitHub Actions workflows using container images.
- Remove container: directive to avoid pre-authentication pulls - Use docker run with volume mounts instead - Pull image after authentication step completes - This allows Docker Hub auth to work before image pulls
- Make Docker Hub authentication conditional on secrets availability - Add retry logic for image pulls with 10 second delay - Fallback from 4.4.1 to 4.3.2 if newer version fails - Use environment variable for dynamic image selection - This should work even without Docker Hub credentials configured
Added repository secrets should now allow authenticated pulls: - DOCKERHUB_USERNAME configured - DOCKERHUB_TOKEN configured This commit triggers a test of the authentication fix.
Key changes: - Add auth-setup job to pre-authenticate and pre-pull Docker images - Use container credentials for direct authentication during pulls - All export jobs depend on both test-suite and auth-setup - Revert to simpler container: directive with credentials - Remove complex Docker run wrapper scripts This should resolve Docker Hub authentication by handling auth before container initialization occurs.
This commit triggers a new workflow run to test the pre-authentication approach with the auth-setup job and container credentials.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
CI/CD workflows were failing with Docker Hub authentication errors:
Root Cause
Docker Hub implemented stricter rate limiting in 2024:
Solution
Added Docker Hub authentication to all container-based CI/CD jobs:
docker/login-action@v3with repository secretscontinue-on-error: truefor graceful fallbackRequired Secrets
This PR requires the following repository secrets to be configured:
DOCKERHUB_USERNAME: Docker Hub usernameDOCKERHUB_TOKEN: Docker Hub access token (not password)Testing
Fixes the Docker Hub rate limiting issues affecting the CI/CD pipeline.