Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: DockerHub Auth Token for third party apps #1419

Closed
ankitvgupta opened this issue Mar 17, 2018 · 12 comments
Closed

Feature Request: DockerHub Auth Token for third party apps #1419

ankitvgupta opened this issue Mar 17, 2018 · 12 comments

Comments

@ankitvgupta
Copy link

ankitvgupta commented Mar 17, 2018

I'm hoping to use DockerHub with CircleCI to host private images and run builds. Right now, to do this, I have to put my DockerHub username and password in CircleCI, as explained here: https://circleci.com/docs/2.0/private-images/

Instead of this, is there a way to add an Auth token that I can share with CircleCI and not other applications? I'd rather not store my password in plain text everywhere.

@damm
Copy link

damm commented Apr 27, 2019

Amazing this issue has been idle for so long with no comments. Please after getting docker hub usernames leaked this would have been a lifesaver

Now I have to cycle my passwords and re-put them back into my CI and wait for you guys to get hacked again :(

Not right

@anguslees
Copy link

To put this in perspective: This is the primary reason I use quay.io to host images that I build externally (not using dockerhub's autobuilder)

@meticulous-dft
Copy link

This item is our top priority.

@ruffsl
Copy link

ruffsl commented Aug 18, 2019

Any official response? I'd rather like to avoid having to create machine user/accounts for everything little thing and adding it to my team/org for it to gain access to our docker repositories. Such workarounds are not very tidy: https://stackoverflow.com/questions/41834554/access-token-for-dockerhub

@damm
Copy link

damm commented Aug 18, 2019

From the lack of response I would say quay.io is looking real good sure it's not free but https://docs.quay.io/glossary/access-token.html

@meticulous-dft
Copy link

Please use personal access tokens for CI systems. https://docs.docker.com/docker-hub/access-tokens/

@ankitvgupta
Copy link
Author

Oh, has this always existed? Thanks very much - this is exactly what I wanted.

@ankitvgupta
Copy link
Author

Ah, I see it's a new feature! Awesome job folks!
https://blog.docker.com/2019/09/docker-hub-new-personal-access-tokens/

@lizrice
Copy link

lizrice commented Jun 3, 2020

It's not a huge deal, but it would be nice if you could generate these access tokens for an organization so that they aren't just associated with and managed by a personal account

@ruffsl
Copy link

ruffsl commented Jun 3, 2020

@lizrice , yep the personal access tokens don't seem to resolve the issue in having to make and endorse personal machine accounts to integrate third party services. This really complicates management of these services within an organization.

@ankitvgupta
Copy link
Author

ankitvgupta commented Jun 3, 2020

fwiw, this is the way Github does things too: https://developer.github.com/v3/guides/managing-deploy-keys/#machine-users

A little lame to have to pay for an extra seat to do this though.

@thaJeztah
Copy link
Member

For further enhancements in this area, I'd recommend opening a ticket in our public roadmap; https://github.com/docker/roadmap. Try to describe your use-case, and why the current implementation does not match your use-case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants