Skip to content
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

update dockerfile to use nightly gluster release6 repo #172

Merged
merged 1 commit into from
Mar 12, 2019

Conversation

Madhu-1
Copy link
Member

@Madhu-1 Madhu-1 commented Mar 12, 2019

Describe what this PR does
update dockerfile to use the nightly gluster release6 repo

Signed-off-by: Madhu Rajanna madhupr007@gmail.com

Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
@ghost ghost assigned Madhu-1 Mar 12, 2019
@ghost ghost added the in progress label Mar 12, 2019
@Madhu-1 Madhu-1 requested review from JohnStrunk and kshlm March 12, 2019 10:01
@Madhu-1
Copy link
Member Author

Madhu-1 commented Mar 12, 2019

gluster/glusterd2#1504

@nixpanic
Copy link
Member

What is the reason for this? Just because "glusterd2 does it" is not a very good explanation :)

@Madhu-1
Copy link
Member Author

Madhu-1 commented Mar 12, 2019

@nixpanic glusterd2 and gluster-csi works together. if glusterd2 uses release6 bits and if we use master bits we may face compatibility issues, keeping both the dependency to same will solve this issue.

@Madhu-1
Copy link
Member Author

Madhu-1 commented Mar 12, 2019

#124

@kshlm kshlm merged commit 1af1068 into gluster:master Mar 12, 2019
@ghost ghost removed the in progress label Mar 12, 2019
@kshlm
Copy link
Member

kshlm commented Mar 12, 2019

Maybe we should move all the GCS container build files into the GCS repo itself. That makes it easier to keep the images inline with each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants