Open EdColeman opened 1 year ago
I can do this
We've never attempted to publish this to DockerHub. And, we should not do so, except for ASF-released versions of the contents of this repository. An ASF release requires a PMC vote, and that release needs to occur before we can publish anything from this to DockerHub. However, we can at least verify that we're registered properly.
The Apache Software Foundation user in Dockerhub has 231 repositories currently listed under it and is identified as a "Sponsored OSS" user. This means it falls under the Docker-Sponsored Open Source (DSOS) program and is exempt from the Free Team Org sunsetting.
Docker continues to offer a specific Docker-Sponsored Open Source (DSOS) program for open source projects, and it is not affected by the sunsetting of Free Team organizations. https://web.docker.com/rs/790-SSB-375/images/privatereposfaq.pdf
Since ASF has an apache dockerhub user, it should own the apache/
org prefix on dockerhub.
Looking at Infra tickets, the registration process seems to be just submitted a ticket to ASF Infra with the request to create a dockerhub repo of apache/accumulo
https://issues.apache.org/jira/browse/INFRA-20220 https://issues.apache.org/jira/browse/INFRA-16647
Individual dockerhub users can be added to the push permissions as well.
https://issues.apache.org/jira/browse/INFRA-18167
This process matches up with the Docker Hub use policy for ASF Infra, which mentions limited seats for DockerHub access. https://infra.apache.org/docker-hub-policy.html
I can't find an infra ticket requesting a dockerhub project be created for accumulo. And apache/accumulo
is not currently listed on dockerhub.
So, I think the next step is submitting an Infra ticket for creation of the apache/accumulo
dockerhub repo.
As I'm not an ASF committer yet, I don't have a JIRA login for submitting the Infra ticket. But if someone else can do that step then I think we can proceed.
This is all separate from actually releasing a docker image and pushing it to the repository.
Thanks for chasing that down.
It may be that with the ASF "owning" the apache org prefix, we (Accumulo) do not need to take any action to "protect" org.apache.accumulo from external registrations.
I feel before submitting tickets and requesting a repo - we should have a discussion on the dev mailing list and decide if we want to start formally releasing docker artifacts.
Docker may be changing registration requirements or process relating to organizations with publishing artifacts in DockerHub. Accumulo docker is likely covered under the Apache umbrella. Check that accumulo-docker is properly registered as an Apache project, and if not, complete the necessary registration process for DockerHub.