-
Notifications
You must be signed in to change notification settings - Fork 7
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
Docker needs authenticating to avoid unauthenticated rate limit. #95
Comments
I think that we should find a way to mount a volume containing the docker config.json or podman auth.json to the lifecycle container we are creating |
This old hack is still working - buildpacks/spec#277 (comment)
|
Signed-off-by: cmoulliard <[email protected]>
I think handling authentication in general is something the library could do better in a future revision. Glad to see that the env var worked.. feels like we should add a section on auth to the docs to cover creation of dockerclient & setting env var appropriately, covering the scenarios where various registries need auth from different places. For as a future feature, we could look at adding json to the ephemeral build container, that would likely be the cleanest way to provide creds to the lifecycle. |
Also, to avoid misunderstanding here..
You received the docker limit error because you have exceeded dockerhub's limits for unauthenticated usage.. the same will not hold true for every user. Executing the code of the build me sample does indeed use dockerhub, but the limits are generous enough that using the samples alone is not enough to trigger that limit. The github action running the tests for this project also runs authenticated and has no issue. I have altered the title of this issue to be clearer. |
This is a better option and also what we do using the Buildpack Tekton's task where we mount such recredentials (= docker.json, etc) from a volume |
Issue
If we execute the code of the Build me sample on a fedora VM running podman 5.2.3 with the sock file, then we got the docker limit error
even if we set the username, password of the dockerclient
Error
The text was updated successfully, but these errors were encountered: