You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user needs to push the resulting image to a private registry they have to give the private registry's credentials, via username and password. This means that every build image will be pulled from DockerHub anonymously. This causes problems on a larger team where you can hit DockerHub's pull rate limit (100pulls/6hours).
Proposal
Allow the user to, alternatively to user/pass, supply a imagePullSecret (like you can with drone) to the plugins/docker container. This would allow a user to give credentials for any number of registries, public and private. Pulling from DockerHub with AccountA and pushing to PrivateReg with AccountB.
The text was updated successfully, but these errors were encountered:
Issue
If a user needs to push the resulting image to a private registry they have to give the private registry's credentials, via
username
andpassword
. This means that every build image will be pulled from DockerHub anonymously. This causes problems on a larger team where you can hit DockerHub's pull rate limit (100pulls/6hours).Proposal
Allow the user to, alternatively to user/pass, supply a imagePullSecret (like you can with drone) to the
plugins/docker
container. This would allow a user to give credentials for any number of registries, public and private. Pulling from DockerHub with AccountA and pushing to PrivateReg with AccountB.The text was updated successfully, but these errors were encountered: