Curator: Publish releases to Docker Hub

[xaka]

Would be nice to have it as official Docker Hub repository in same way as it's done for https://hub.docker.com/_/elasticsearch/. You already have Dockerfile in place so it's matter of automation I guess. Thanks!

[svenmueller]

+1

[jakommo]

Not a real answer but please note https://hub.docker.com/_/elasticsearch/ is not developed or provided by Elastic. It's just an "official" docker library image.

[untergeek]

When Elastic releases "official," Elastic-provided docker images, then we might release this. Until then, it's on-hold.

[czerasz]

Published an image with curator 4.0.1 if someone needs it.

Already tested it and it works nice :-)

[davidkarlsen]

@untergeek it's about time now - since elastic publishes official images of kibana and elastic. Also the one in the library is currently lacking support for 5.1.1.

[untergeek]

For anyone else looking here, until further notice, I would recommend using https://hub.docker.com/r/bobrik/curator/

[praseodym]

I've also created an automated Curator Docker image build based on the official Python 3-alpine image.

It is available from both Docker Hub and Quay:

• https://hub.docker.com/r/praseodym/elasticsearch-curator/tags/
• https://quay.io/repository/praseodym/elasticsearch-curator?tab=tags

[davidkarlsen]

Great - it would be even more great if elastic inc would curate this image along the rest of ELK

[geekofalltrades]

@untergeek , any motion on this? I'm about to start deploying ELK stacks in Kubernetes, and I'd love to see curator up alongside the others on docker.elastic.co.

[frittentheke]

@untergeek Since your already have a Dockerfile yourself, wouldn't it make sense to have a somewhat offical image published somewhere? Otherwise everyone and their cat is simply forking your code at some point to create their own images with likely no real maintenance or updates.

[MaikJaek]

@untergeek
Hi Aaron,

do you have any news regarding the suggested idea of publishing images on docker.elastic.co ? We'd love to use an official image for curator, as well.

[pete-woods]

Given you now publish official Docker images to https://www.docker.elastic.co/, is it the right time to start publishing this, too?

[untergeek]

Sorry everyone, for the prolonged delay in response. Yes, I would like to offer an official Elastic Curator image. Not sure yet when this will happen. It probably won’t be until the next major version is released. And I’m not sure when that will be.

At the end of the day, Curator is still a one-man show (me), and I am a consultant now, rather than a full-time developer, so my development time is more limited. Coming soon will be Index Lifecycle Management, which will cover the most common Curator use cases, complete with a UI in Kibana. For anything requiring more complicated flows, Curator will continue to be the go-to tool for index management. As such, yes, an official Docker image is an important step. I will get to it when I can, as it involves me working with the infra team that does image publishing, etc. I will get to it when I can, but it will not be the next few weeks, what with the holidays coming.

[pete-woods]

It's about a 5 minute job to set up an automated Docker Hub image, in case you haven't done it before. I'd be happy to take it from there instead of the Elastic repo.

[frittentheke]

@untergeek please also accept my offer to assist with setting things up. This really only takes a few minutes when using Travis CI ... https://ops.tips/blog/travis-ci-push-docker-image/

[untergeek]

I appreciate the offer, @frittentheke. However, if it were as simple as that, I would already have done it. There are internal and external politics and multiple systems involved. Our infra team manages the docker hub images. I have to go through them. Curator is not deployed or managed on those Jenkins servers, which manage the automated building process. I have to go through a process to get things on their servers if I want this to happen. It's not high enough on the priority list to escalate and get Curator both on the internal build system and in Docker Hub in an expedited time frame—especially not since Index Lifecycle Management is almost ready for release.

[pete-woods]

You don't even need Jenkins, TravisCI, etc if you use Docker Hub, it has its own builders. At the minute I'm having to use a GitHub mirror of your repo to set up automated builds to here.

https://hub.docker.com/r/surevinecom/elastic-curator/

[untergeek]

You’re right, but that’s not the point. My Infra team manages all docker building and publishing. I can’t be a one-off.

[jippi]

@untergeek any plans for a 2019 fix for this? :) would be highly appreciated

[frittentheke]

@untergeek especially with all your great new releases and the recommended image from bobrik not running automated builds / pushes to DockerHub (https://hub.docker.com/r/bobrik/curator/tags) this would be awesome to have.

[eyalzek]

An official image for 5.7 would be greatly appreciated :)

[untergeek]

I may never push (or be able to push) Docker builds of Curator to the docker.elastic.co repository, but I will start publishing builds of the Dockerfile in GitHub to untergeek/curator:major.minor.patch.

Starting with version 5.7.6, this is now available:

docker pull untergeek/curator:5.7.6

Please note this is the curator binary, and not curator_cli.

[guessi]

@untergeek good to know there's an update from the author :tada:

But still looking forward for image build & push automation being integrated. Test automation have being integrated into .travis.yaml, adding a new step for image build automation shouldn't be a problem.

The only concern would be which shared account would be used for build automation, privileged user(s) could have change to retrieve the secrets, or leak via a bad pull-request, is that the reason for not having that docker image build automation?

btw, you might want to fix the repo link in the comment above,

• From: https://cloud.docker.com/u/untergeek/repository/docker/untergeek/curator (5xx error)
• To: https://cloud.docker.com/repository/docker/untergeek/curator

[untergeek]

I will not be automating anything in the foreseeable future. I just don't care enough. I will happily publish releases to Docker Hub at the same time I add RPM/DEB packages, Windows MSI/ZIP, and the PyPI releases. They will be in perfect sync that way, as well as release tested (not just CI).

[koshatul]

Sorry to resurrect an old issue, but I made an automated build of the curator repo into docker hub using Github Actions (so I don't have to maintain it and keep updating for new versions).

https://hub.docker.com/r/koshatul/curator/tags

Is it OK to leave it going ?