Skip to content

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:

      image: octocat/ci-image:latest
        username: mona
        password: ${{ secrets.docker_hub_password}}
          username: ${{ github.repository_owner }}
          password: ${{ secrets.ghcr_password }}

For questions, visit the GitHub Actions community forum.

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

Logs for GitHub Actions have gotten a significant update. Some major enhancements and new features include:

  • Styling changes to improve readability
  • An improved search experience for large logs
  • Auto-scrolling and expansion if a step fails
  • Redesigned errors and warnings
  • Clickable URLs
  • Support for more colors
  • Full-screen mode

Check out our detailed blog post on the new Logs Experience for more information.

For questions please visit the GitHub Actions community forum

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

See more