Skip to main content

Docker Success Center

The Docker enterprise customer portal.

Docker, Inc.

Can’t access new GitHub organization for automated builds

Overview

After creating an Automated Build from a GitHub organization and making changes, the settings aren't correct, and the GitHub organization is not accessible from Docker Hub.

Scenario

Created a new organization on GitHub
Created a repository inside the new organization

In Docker Hub:
- GitHub account is linked to Docker Hub for Automated Builds
- A new repo is created for Automated Builds

Issue: can't see that new organization

Resolution 

You may need to revoke the GitHub access and then request access on your repos when relinking.

You should do the following:

  1. Unlink your GitHub account at Docker Hub: https://hub.docker.com/account/authorized-services/
  2. Revoke the Docker Hub Registry application on your GitHub account: https://github.com/settings/applications26
  3. Link to your GitHub account again using Public & Private Accesshttps://hub.docker.com/account/authorized-services/
  4. On the Authorize Application page, make sure that all of the organizations you need access to have a green check mark, otherwise click the Request Access button.

Note: There has been a change with the GitHub API, so public and private access is required at the moment. We do have an internal ticket open to fix the limited access.

Also, if you're using a GitHub organization, your profile on your organization's people page (https://github.com/orgs/**your-org**/people) has to be set to public.