Share and learn in the Docker community.
Created a new organization on GitHub.
Created a repo inside the new org
In docker hub
We’ve already tried unlinking and linking back GitHub to DockerHub but we still can’t see the new GitHub org and it’s repos
I have the exact same problem here…
The GitHub repos of my GitHub organization (pyannote) do not appear in the list (only my personal GitHub repos do) – even though I am a public member of this GitHub organization.
It is strange as, in the past, I did manage to setup automated builds for repos from this GitHub organization – they are still working by the way… (see pyannote/core for instance).
Github recently changed their API. We have an internal ticket open to solve this problem.
Hervé: Could you try unlinking and then relinking with the Public and Private option and see if that takes care of it for you?
Miriam: It looks like you’re already set with the Public/Private option. When you unlinked, did you make sure that all Docker related links were removed from Github? - At github.com > Settings > Applications.
So far, those accounts that have unlinked, then selected Public/Private on the re-link have worked successfully.
Thanks,
Jerry
Hi Jerry,
Sorry for the delay in answering…
Unlinking and relinking with “Public and Private” option worked for me — though I am not sure I want to give Docker Hub write access to my repos…
Hervé.
Hi Jerry,
Sorry for the delay
Unlinking, removing all docker hub access in my github and linking again works for me. Thanks
Re-linking did not work for me 
Any other suggestion?
Morning benzaita,
You may need to revoke the Github access and then request access on your repos when relinking.
Could you try the following:
Note: Public and Private access is required at the moment - There has been a change with the github API. 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.
Thanks,
Jerry
Jerry, thanks for the prompt response. The procedure you suggested fixed the problem.
Has the limited account access been fixed? I was unsuccessful at adding a Github organization for automated builds using limited access. I would rather not grant read/write access to all organizations if possible.
Is there any word on the progress of the internal ticket? Would very much like to have the limited access automated builds back 
Any update on getting limited access to work?
For those experiencing this issue with new organizations not being syncronized, you should be able to force this working by doing the following:
Docker Hub doesn’t allow the creation of an organization with a dash (hyphen) in the name. Any workaround?
Thx
I am still unable to re-link our Docker Hub or Docker Cloud account to a new GitHub organisation and have it show up as an available choice when trying to link a repo created in Docker Cloud with a GitHub repo.
I tried revoking access from GitHub for Docker Hub and Docker Cloud, unlinking from Docker Hub and Docker Cloud, and relinking both Docker Hub and Docker cloud to a public member account of the new GitHub organisation.
I chose the public/private option when linking Docker Hub.
Linking Docker Cloud gave me no choice.
GitHub show that both Docker Hub and Docker Cloud applications are authorised.
Both Docker Hub and Docker Cloud show that they are linked.
And yet, I still can’t see the new GitHub organisation when trying to configure auto-builds for a Docker Cloud repo.
In case your Github organisation doesn’t appear in Docker you should make sure that the Docker hub is allowed to access the Github organisation.
You can check it on the Github Organisation settings under the Authorised applications
This was incredibly frustrating. In the github organization I ended up having to change github third-party application access to unrestricted, which is less than desireable. Perhaps because my account was the github organization owner, maybe there was a difference in workflow from that of a normal user, and the third-party access request was never triggered back on the organization?
Really hoping someone looks into this one.
This solution, even if not really elegant, works fine !
Since it’s been a year, can we assume that the internal ticket to get the public access fixed has been abandoned? The odd thing for us is that the public read-only link we set up before the API change still works, but this is blocking us from adding new products with automated builds (giving Docker Hub unrestricted access to our github repository is not an option).
New GitHub org wouldn’t show up for me in Cloud Auto Builds even after making myself public member of that org and been given owner status. Then I found in GitHub no one had approved in org settings under Third-party application access policy for “Docker Cloud Builder”, and once I approved that, it showed up in Docker Cloud automated builds pulldown within minutes.
This solution did not work for me. It got me to the correct page, but when I attempted to create the automated build, it would simply hang (https://github.com/everhartlab/sclerotinia-366-dependencies/issues/2).
I WAS able to create an automated build via cloud, but there are other issues with this:
Note that I was able to get everything working from a fork of this repository in docker hub: https://hub.docker.com/r/zkamvar/sclerotinia-366-dependencies/