Open ryanmoran opened 3 years ago
Hi, I think Docker OpenSource Program should be applied for paketobuildpacks
and paketocommunity
in order to get unlimited pulls.
The Paketo project is part of the CloudFoundry Foundation, so we should be a verified OSS project with Docker. Let me know if you are seeing rate-limiting pulling any of the images from paketobuildpacks/*
or paketocommunity/*
.
I thought something like this should be displayed.
I wonder if that is new? Let me ask around in the CFF and see. I'm pretty sure the CFF is part of this program, it was specifically listed in the original Docker blog post that announced it. I'll see if we can get those badges :)
It took a little while but the Java and Rust Buildpacks should be on Docker Hub this week when we publish on Friday.
That should close out this issue.
This is mostly a documentation project at this point. I believe we still have a number of locations across the project where we reference our image distributions by their GCR location. We should update these to point to Docker Hub.
Oh, I forgot to update. On the badges I asked Chris at the CFF about this and he said they are still working on getting this straightened out with Docker. Images published under paketobuildpacks/
should not have rate limits, cause we are a qualified OSS project, but we don't have the purple badge. Hopefully the CFF can sort that out.
RFC
Summary
In addition to the current Google Container Registry (GCR) distribution channel, buildpacks should be distributed via Docker Hub.
paketobuildpacks
DockerHub accountpaketocommunity
DockerHub accountpackage.toml
references in language-family buildpacks