-
Notifications
You must be signed in to change notification settings - Fork 344
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
Comments
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). |
@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. |
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) |
In light of #160 and the discussion there, I think that this issue can be closed now? |
Update Kibana label timestamps to correspond to those in the published image.
No description provided.
The text was updated successfully, but these errors were encountered: