Skip to content

Clarify "official #66

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

Closed
markwalkom opened this issue Nov 1, 2015 · 4 comments
Closed

Clarify "official #66

markwalkom opened this issue Nov 1, 2015 · 4 comments

Comments

@markwalkom
Copy link

No description provided.

@yosifkit
Copy link
Member

yosifkit commented Nov 3, 2015

The Docker Official Repositories are a curated set of Docker repositories that are promoted on Docker Hub.
https://docs.docker.com/docker-hub/official_repos/

We would definitely be interested if upstream elastic would be interested in maintaining their Official Images or even involved in any way 😄. We have some info on how to take over: https://github.com/docker-library/official-images#maintainership. The gist is get involved. The sentry image was transferred quite quick since they were already involved (getsentry/docker-sentry#19).

@psftw
Copy link

psftw commented Nov 4, 2015

@markwalkom please reach out to me directly (ps@docker.com) if you have any particular concerns after reading up on the links above. It's not uncommon for an upstream vendor to be involved in both an Official Repository and also maintain their own releases under an organization account on DockerHub (i.e. neo4j and neo4j/neo4j). Our engineering team has endorsed Found, and we are looking to strengthen the relationship in other ways in the near future.

@markwalkom
Copy link
Author

Sorry, I kinda let this one slide!

I think (not to be taken as the official truth ;)) we would be interested in eventually managing this as an official image, but we've just had a few people hit us up directly because of the "official" tag and have made the assumption we already are.

That last part is just want could be clarified.

(Apologies for the crap OP too)

@jasontedor
Copy link
Contributor

In light of #160 and the discussion there, I think that this issue can be closed now?

1gtm pushed a commit to appscode-images/elasticsearch that referenced this issue Feb 14, 2024
Update Kibana label timestamps to correspond to those in the published
image.
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

No branches or pull requests

4 participants