Skip to content
Frequently asked questions

Frequently asked questions

Docker rate limiting

In November 2020 Docker Hub started rate limiting anonymous accounts. Occasionally, you will get rate limited, as you're sharing the outgoing IP with other runs within the BuildJet network. And as GitHub Actions have a custom deal with Docker Hub, you might never have seen this error with the native runners.

To fix this, we simply suggest you get a free Docker Hub account. It's pretty straightforward. You can start by creating an account here and then following the FAQ item on how to authenticate GitHub Actions jobs.

Authenticate container and services

Job and Service containers in GitHub Actions allow you to containerize your CI environment and make databases, caches, or other services available to your tests. As, we don't have a custom deal with Docker Hub, you need to authenticate those as well. However, this is not possible with the Docker Login Action as described above.

Doing authenticating the containers is quite straightforward. Simply create a secret in your workflow and use them in container and services credentials to set the username and password.

jobs:
  build:
    container:
      image: node:10.16-jessie
      credentials:
        username: ${{ secrets.docker_hub_username }}
        password: ${{ secrets.docker_hub_password}}
    services:
      db:
        image: node:10.16-jessie
        credentials:
          username: ${{ secrets.docker_hub_username }}
          password: ${{ secrets.docker_hub_password}}

Your current GitHub Actions usage

GitHub Actions provides this data in their Accounts page. For detailed instructions follow this link: here

MacOS Support

We are waiting for the M1 ecosystem to mature. Unfortunately, hard to promise any time frame when this will happen. GitHub already offers Intel Mac runners, if we go with that, we'd offer the same speed as GitHub.

We did try setting it up for M1, but had too many compatibility issues for it to be a smooth experience. Usually, customers who need apple, use GitHub's default macOS runner for the Apple tasks and our Linux runners for other tasks.

VM in VM support

Yes, it is possible.

Do you support everything GitHub Actions supports?

Yes, we do! The runner operating system is effectively identical to GitHub Actions and as we only provide the hardware for your runs, everything that is supported by GitHub Actions is also supported by BuildJet.

GitHub Enterprise support

We technically work with GitHub enterprise, but as they usually involve custom setups, there might be things we need to customize to integrate with. Please contact customer support, and we will help you out.