Bug 1686034 - Request access to docker hub gluster organisation.
Summary: Request access to docker hub gluster organisation.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: experimental
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-06 15:13 UTC by Sridhar Seshasayee
Modified: 2019-03-08 04:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-08 04:34:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Sridhar Seshasayee 2019-03-06 15:13:43 UTC
Description of problem:
I request access to the docker hub gluster organisation in order to push and manage docker images. My docker hub user ID is: sseshasa

I am not sure what to choose for "Product" and "Component" fields. Please suggest/correct accordingly if they are wrong.

Version-Release number of selected component (if applicable):
NA

How reproducible:
NA

Steps to Reproduce:
1.
2.
3.

Actual results:
NA

Expected results:
NA

Additional info:
NA

Comment 1 M. Scherer 2019-03-06 15:18:23 UTC
So, what is the exact plan ? Shouldn't the docker image be built and pushed automatically ?

Comment 2 Sridhar Seshasayee 2019-03-06 15:34:38 UTC
I have built a docker image locally and pushed it to my repository on docker hub with user ID: sseshasa.

However, I need to push the same image under the gluster organisation on docker hub (https://hub.docker.com/u/gluster) under gluster/gluster*. I don't know how to achieve this and imagine that I need some access privilege to push images there. Please let me know how I can go about this.

Comment 3 M. Scherer 2019-03-06 15:59:06 UTC
Nope, we do not allow direct push (or shouldn't). If you want a new image there, you have to explain what it is, why it should be there, etc, etc. And automate the push, for example, using a jenkins job. See for example this job: 
https://build.gluster.org/job/glusterd2-containers/ 

http://git.gluster.org/cgit/build-jobs.git/tree/build-gluster-org/jobs/glusterd2-containers.yml 

that's managed by gerrit, like the glusterfs source code.

Comment 4 Sridhar Seshasayee 2019-03-07 05:24:49 UTC
Okay, thanks for the info and pointers. I will work with one of the developers and get this done. This issue may be closed.


Note You need to log in before you can comment on or make changes to this bug.