Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] DockerHub starts enforcing limits in organization membership

I'm sorry I mistakenly replied to this message when it was meant for another one regarding GitHub Actions.

On Tue, Mar 23, 2021 at 6:25 AM Mikael Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Kevin,

This is not related to github, just to Docker Hub. And yes, we are working on a solution via


Mikaël Barbero 
Manager — Release Engineering and Technology | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

On 23 Mar 2021, at 14:05, Kevin Herron <kevinherron@xxxxxxxxx> wrote:


Some time back on this list I read that it was now possible for your project to request to be its own top-level organization, which would mean you are not subject to the shared org-wide limitations.

I think you just need to open a bug against Community/GitHub and ask for assistance.

Maybe there is an easier solution in the works, though...


On Mon, Mar 22, 2021 at 6:44 AM Mikael Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi everyone,

(cross posted to cbi-dev and

Until now, we've been managing DockerHub hosting request as per the following gules (copied from

The Eclipse Foundation owns the eclipse organization and a couple of other project specific organizations at You can ask to get a repository being created on one of these organizations. We will set permissions so that committers have write access to this repo (you will need to share your Docker Hub ID with us).

You can also ask us to create a project specific organization. The organization name needs to follow the pattern eclipse<projectname>.

Note that we don't grant admin permissions on any Eclipse Foundation owned organization. We recognize that this means that you will have to go through us for all new repo creation, but we can't grant organizations-wide admin permission assigned to committers for security reasons.

When we add people (and bots) to teams (in order to grant them write permissions on repositories), they are automatically added to the corresponding organization as member. Until now, we were able to add as many members as we wanted to. But 10 days ago we discovered via bug 571598 that the number of (free) members is now limited to 3. See, and for details.

We are largely surpassing this number on all the organizations we manage (see below a screenshot of the eclipse organization members counter for example). As such and effective immediately, we cannot grant access to anyone new to our existing managed organizations and for new organizations. We can only grant write access to a single committer (we keep one seat for webmaster and one seat for a bot user). We are also expecting DockerHub to start removing member from the various organization. If you lose your write permissions on some repository, please open a ticket.

We are quite surprised by this change as we did not read or heard about such policy change at docker hub. You may remember about the pull rate policy change announced back in August ( and enforced last October (, but we did not see any message similar about Free Teams. 

We need to find a solution moving forward. Some time ago, we opened bug 559659 to start discussing better integration with a container registry provider. I propose we continue discussing over there about how to move forward on that topic.



Mikaël Barbero 
Manager — Release Engineering and Technology | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

_______________________________________________ mailing list
To unsubscribe from this list, visit

Back to the top