GitHub Actions: Private registry support for job and service containers

You can now use images from private registries in job and service containers.

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. Previously those containers had to come from a public container registry which limited the usefulness for some customers. Additionally, we had numerous requests from the GitHub community forums for private registry support.

Here’s an example of using private images from Docker Hub and GitHub Container Registry:

jobs:
  build:
    container:
      image: octocat/ci-image:latest
      credentials:
        username: mona
        password: $
    services:
      db:
        image:  ghcr.io/octocat/testdb:latest
        credentials:
          username: $
          password: $

jobs:
  build:
    container:
      image: octocat/ci-image:latest
      credentials:
        username: mona
        password: $
    services:
      db:
        image:  ghcr.io/octocat/testdb:latest
        credentials:
          username: $
          password: $

For questions, visit the GitHub Actions community forum.

To see what’s next for GitHub Actions, visit our public roadmap.