Clarify upstream support

[jasontedor]

This commit clarifies that upstream is not involved with the Docker Hub image. This is an important clarification as the Docker Hub definition states:

This team works in collaboration with upstream software maintainers, security experts, and the broader Docker community.

For this image this is not correct. As this causes confusion within the Docker and Elasticsearch communities, it's important to clarify these remarks.

Relates #66

[tianon]

Thanks @jasontedor ❤️ (and sorry for any confusion the unfortunate name choice for this program has caused 😞)

I'm going to merge this, but I'd also like to take the opportunity to once again invite anyone from Elastic upstream to collaborate with us. Additionally, if you'd prefer, we can deprecate our images and point folks to your images, but we'd really rather work together to make something good. ❤️

[jasontedor]

Thanks for being so understanding @tianon ❤️, we are genuinely only looking for what's best for the community of both Docker users (which we are ourselves) and Elasticsearch users.

As we fully support our images, I think that our preference would be that we use our infrastructure to deliver/support/maintain them. Our preference would be to deprecate this image and point to the official, fully-supported Elasticsearch images. We sincerely appreciate this move. Would you mind clarifying what deprecation entails (we do not want to leave any current users stranded if they elect to cut over to our images)?

[yosifkit]

Previously for deprecated images, we chose a date at least a few months out after which there would no longer be updates to the images. We then add a big warning to the documentation that appears on the Docker Hub so that users will discover that it will be deprecated. We can decide together when that would be best for elastic.co images. My initial thought is to pick something like end of May or June, but really as fast or slow as you desire. Does the team at elastic.co maintain elasticsearch, logstash, and kibana images? Do we want to deprecate all of them together?

[jasontedor]

We can decide together when that would be best for elastic.co images. My initial thought is to pick something like end of May or June, but really as fast or slow as you desire.

A few months sounds reasonable to me. I will discuss this specific proposal with some folks internally and come back to confirm.

Does the team at elastic.co maintain elasticsearch, logstash, and kibana images? Do we want to deprecate all of them together?

Yes, we maintain images for all three. I think that it makes sense to deprecate them all together (all three products are on an identical release cycle).

I want to say again how appreciative we are of the response and discussion here, truly admirable.

[yosifkit]

Still a little sad that the images will be leaving the official images program, but I understand that our process is a little onerous and may not fit within your processes. Thanks for understanding.

[jasontedor]

We can decide together when that would be best for elastic.co images. My initial thought is to pick something like end of May or June, but really as fast or slow as you desire.

A few months sounds reasonable to me. I will discuss this specific proposal with some folks internally and come back to confirm.

@yosifkit We would like to propose June 20 (four months from now).

[yosifkit]

Sounds reasonable to me. @tianon and I will work on a PR and then ping you so that we can get the right wording for the deprecation notice.

[twang2218]

@jasontedor Just found out elasticsearch, kibana and logstash moved away from Docker Hub, which is very sad for users in China.

Because, usually we cannot access the image registry server outside GFW, say gcr.io as example, but, fortunately, we have docker registry mirror services for Docker Hub, so we can access any docker images available on Docker Hub via registry mirror server.

Now, docker images for ELK stacks moved away from Docker Hub will definitely caused trouble for us. I hope you reconsidering that publishing the docker images to docker hub as well. Thanks.

[jasontedor]

@twang2218 Thank you for sharing this concern, I take this impact on the community seriously. I want to be clear about something: the images that were on Docker Hub were never produced by Elastic yet I will raise this within Elastic and we will explore options here.

[twang2218]

@jasontedor Thanks for your reply. I understand these docker images were not produced by Elastic team, however, I believe docker team tried their best to make the high quality docker images. Then, why not cooperate with Docker Team and make this repo real official? It should be win-win for all of us.

[c4milo]

This is very sad, especially when I see no good Alpine alternatives offered by ElasticCO.

[gerrith3]

@jasontedor do you also still have docker images for POWER (ppc64le) and Z available? If not, we would be willing to help create those.

[jasontedor]

@gerrith3 Elastic does not make available images for those systems; we only officially support Linux and Windows (for production) and unofficially macOS (for developers).

[gerrith3]

What can IBM do to help you make those available? We see this as a common request on Linux on POWER. We can provide an unofficial version, obviously, and normally with with Docker.com and Tianon on providing multi-platform containers. What is your process for doing so now since this is no longer an official docker.com image? gerrit

…

-- "Only those who will risk going too far can possibly find out how far one can go." ~ T. S. Eliot Gerrit Huizenga, STSM Power Open Source Ecosystem Lead gerrit@us.ibm.com From: Jason Tedor <notifications@github.com> To: docker-library/elasticsearch <elasticsearch@noreply.github.com> Cc: Gerrit Huizenga <gerrit@us.ibm.com>, Mention <mention@noreply.github.com> Date: 08/27/2017 05:10 PM Subject: Re: [docker-library/elasticsearch] Clarify upstream support (#160) @gerrith3 Elastic does not make available images for those systems; we only officially support Linux and Windows (for production) and unofficially macOS (for developers). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.