Sonarqube-scan-action and Docker Hub Rate Limits

SonarQube Server / Community Build
1

I use private runners for GitHub Actions. I’m trying to use the sonarqube-scan-action in my workflows, but I’m running into Docker Hub rate limit issues.

This action is a Docker action, where GitHub Actions has to build the provided Dockerfile first. It does this build as a prerequisite step in the workflow, even before my step that logs into Docker Hub. This means the pull from Docker Hub is unauthenticated.

Here’s a GitHub discussion on this exact issue, with no real solution yet.

Does this action need to be a Docker action? Or, alternatively, can you host the referenced image on another registry, like ghcr.io?

4

Hi @nnellansadusa, we have good news!

We have recently released a new version of the GitHub Action, v4.0.0, that removes Docker and moves to a GitHub composite action.
You can find the new release here and all the details about it in this community post.

That should solve your issues with the Docker Hub rate limit. Give it a try and let us know if the new version of the action works for you.

Best regards,
Antonio

3 Likes
5

That’s great news, thank you very much!

1 Like