Requesting Docker Hub access
How to request a just-in-time role in a Docker Hub organization via P0
Request a just-in-time member, editor or owner role in a Docker Hub organization through P0. If you're already in the organization, P0 changes your role when your request is approved, and puts your previous role back when access ends. If you aren't, P0 invites you to the organization with the role you requested, and takes back the invite or your membership when access ends.
Requesting from the P0 CLI
p0 request docker role <organization> <role><organization>
The organization's name on Docker Hub, as in its repositories' names: <organization>/<repository>.
<role>
The role you need: member, editor or owner. See Roles.
For example, to request the editor role in my-docker-org:
p0 request docker role my-docker-org editor --reason "Create the repository for the billing service"You can request only the organizations that your admin installed in P0, and you can hold one request per organization at a time. While an earlier request of yours for an organization awaits approval, or is approved or active, P0 refuses a new one for it. Relinquish the earlier request once it's active, or wait for it to be denied or to expire, then request again. P0 also refuses one while it hasn't finished removing the access an earlier request gave you. A request that failed when P0 granted it doesn't stop you from requesting again. See When P0 refuses your request.
Requesting from Slack or the P0 app
In Slack, the same command works as a slash command: /p0 request docker role <organization> <role>. To fill in a form instead, type /p0 request in Slack, or click Request Access on the Access Management page of the P0 app, then select Docker Hub and choose the Organization and the Role.
For every way to request access, see Requesting access.
Roles
You can request any of Docker's three core organization roles:
Member
member
Basic access, with no administration. A member can see the organization's other members, and pull images from the repositories they have access to.
Editor
editor
Partial administration. An editor can create, edit and delete repositories.
Owner
owner
Full administration of the organization, including its repositories, teams, members and billing.
For everything each role can do, see Docker's core roles.
You can't request an organization's custom roles, and if you hold a custom role in the organization, you can't request any role there. You also can't request the role you already hold in the organization, or a lower one.
When your request is approved
What P0 does depends on whether you're in the organization:
If you're a member of the organization, P0 changes your role to the one you requested.
If you aren't, P0 invites you to the organization at the email you sign in to P0 with, with the role you requested. Accept the invite to join.
P0 looks you up again when your request is approved, and that lookup decides. If you joined the organization after you requested, P0 changes your role instead of inviting you.
Your access time starts when P0 sends the invite, not when you accept it, so accept it soon. Until you do, the invite takes one of the organization's seats.
When your access ends
When your access expires, or you or an approver end it early, P0 takes back what it gave you:
If you were a member before the grant, P0 puts your role back to the one you had before. When that lowers your role, P0 always does it, even if someone raised your role in Docker Hub during the grant, and overwrites their change. When it would raise your role, because an admin lowered it below the one you had before the grant, P0 does it only while your email domain is still allowed and your Docker email is still your P0 email. Otherwise you keep the lower role. If you've left the organization by then, P0 changes nothing.
If P0 invited you, P0 puts the organization back as it was before your request: it cancels every pending invite to your email, and removes you from the organization, whatever your role is by then. If P0 never finished granting your request, it cancels any pending invite to your email but removes no one.
When P0 refuses your request
P0 refuses a request as you make it in these cases:
You already have the <role> role in <org>.
You already hold the role you asked for, or a higher one. The message names the role you hold.
You don't need to request it.
You have a custom role in <org>. P0 can't change custom roles yet.
Your role in the organization is one of its custom roles, not member, editor or owner. A custom role named like a core role in another letter case, such as Member, is a custom role too.
Ask an owner of the organization for the access you need.
You have a pending invite to <org>. Accept it, or ask an owner of <org> to cancel it. Then request again.
The organization has invited you, and you haven't accepted. The invite can be one that an earlier request of yours left behind when P0 couldn't finish granting it.
Accept the invite, or ask an owner of the organization to cancel it in Docker Home. Then request again. If P0's request failed and left the invite behind, accepting it gives you the role with no end date, so ask an owner to cancel it instead.
You already have an open Docker Hub request for <org>.
An earlier request of yours for this organization awaits approval, or is approved or active.
Wait for that request to be denied or to expire, or relinquish it once it's active, as in Relinquishing access. Then request again.
P0 couldn't finish removing your previous access to <org>. Ask an admin to fix it in Docker Hub and finish the revoke in P0, then request again.
An earlier request of yours for this organization ended, and P0 couldn't remove the access it gave you.
An admin fixes the cause of that failure, as in On requests, and clicks Retry revoke on the earlier request. Then request again.
P0 checks these again after your request is approved, so you can also see them then.
Troubleshooting
<role> isn't a role P0 can grant in Docker Hub. Request member, editor or owner.
Request one of the three Roles.
P0 is not installed for the organization '<org>'. Check the spelling, or ask your P0 admin to install it.
Check the organization's spelling. If it's right, an admin installs Docker Hub for that organization.
Your email domain isn't allowed for Docker Hub organization <org>. Ask your P0 admin to check the connector's allowed domains.
Your P0 email's domain isn't one that your admin allows for this organization. An admin changes the allowed domains, as in Step 2: Set the allowed domains.
More than one member of <org> has the email <email>. Ask your Docker Hub admin to fix this.
Two Docker accounts in the organization have your email. An owner of the organization removes one, or changes its email. Then request again.
Your Docker account changed after you requested access. Request access again.
The Docker account P0 found when you requested isn't the one it finds now. Usually your Docker account's email is no longer the email you sign in to P0 with. It can also mean you left the organization, or your username now belongs to another account. P0 changed nothing. If your Docker email changed, set it back to your P0 email, then make a new request. If you've left the organization, a new request invites you.
You joined <org> after you requested access. Request access again.
You weren't in the organization when P0 looked you up after approval, but you were when it went to send your invite. P0 sent no invite and changed nothing. Make a new request, and P0 changes your role instead of inviting you.
Docker Hub says you're already in <org>, but no member has the email <email>. Your Docker account probably uses a different email. Ask your Docker Hub admin to check it.
Your Docker account is in the organization under another email than your P0 email, so P0 didn't find you there. Set your Docker account's email to the email you sign in to P0 with, then request again.
Docker Hub refused the invite to <org>: <reason>.
Docker Hub's reason says what's wrong. If the organization has no seat left, an owner of the organization frees one or adds one. Then request again.
Docker Hub refused to cancel one of the pending invites to <org>: <reason>
When your access ended, P0 couldn't cancel every pending invite to your email. An owner of the organization cancels the rest, as in On requests.
Docker Hub refused to remove <username> from <org>: <reason>. P0 cancelled the pending invite to <email>, but <username> is still a member of <org>., or the same message with the number of invites P0 cancelled
When your access ended, P0 cancelled the pending invite to your email, but Docker Hub refused to remove you from the organization, so you're still in it. An owner of the organization fixes what Docker Hub's reason names, as in On requests.
Docker Hub couldn't find <username> in <org>. Check that it still exists, and that the organization access token is for <org>., or the same message naming only <org>
Docker Hub has no such member, or no such organization for the token P0 uses. If you left the organization, request again, and P0 invites you. Otherwise an admin checks the install, as in On requests.
Docker Hub refused the connector's request for <org> (<status>): <reason>
Docker Hub wouldn't make the change, and its reason says why. An owner of the organization fixes what it names. Then request again.
Docker Hub is temporarily unavailable. Try again in a few minutes.
Docker Hub is limiting requests from P0's connector, or the connector couldn't reach Docker Hub. Try again in a few minutes.
P0 couldn't reach the Docker Hub connector. Ask your P0 admin to check its deployment.
An admin checks that the connector is deployed, and that P0 can invoke it.
P0's Docker Hub connector couldn't read the organization access token. Ask your P0 admin to check the Docker Hub install.
An admin checks the token's secret, as in On requests.
A message that starts There is an unrecoverable error in your organization's Docker Hub installation
Docker Hub didn't accept the organization's access token. An admin stores a current token, as in Change the install later.
The Docker Hub connector for <org> isn't installed, so P0 can't change roles in <org>. Ask your P0 admin to install it. Access that P0 already granted in <org> may need to be removed by hand.
An admin installs the organization's connector, as in On requests.
Last updated