# Missing (few) official Docker images

**URL:** <https://discuss.elastic.co/t/missing-few-official-docker-images/160138>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [December 10, 2018, 10:02am UTC](https://discuss.elastic.co/t/missing-few-official-docker-images/160138 "2018-12-10T10:02:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![renan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/renan/32/38627_2.png) [@renan](https://discuss.elastic.co/u/renan)\
**Post date:** [December 10, 2018, 10:02am UTC](https://discuss.elastic.co/t/missing-few-official-docker-images/160138/1 "2018-12-10T10:02:08Z")

</div>

At Werkspot (part of IAC / HomeAdvisor US) we extensively use Elastic products for both full-text search for our platform and for our centralized logging system.

As we are migrating our stack to run on top of Kubernetes we could find a number of Docker images at [https://www.docker.elastic.co/](https://www.docker.elastic.co/). That is great, we love getting images from official/trusted places.

Few images we can't find in there, however, namely:

- Curator (from [https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html)) we now use [https://hub.docker.com/r/bobrik/curator/](https://hub.docker.com/r/bobrik/curator/)

- Journalbeat (from [https://github.com/elastic/beats/pull/8703](https://github.com/elastic/beats/pull/8703)) we now use my own fork of it from [https://hub.docker.com/r/renang/journalbeat/](https://hub.docker.com/r/renang/journalbeat/)

If you see where this is going, I would like to request that those images are also included in the official registry you folks manage. Would that be possible?

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [December 10, 2018, 1:12pm UTC](https://discuss.elastic.co/t/missing-few-official-docker-images/160138/2 "2018-12-10T13:12:19Z")

</div>

There is no official Curator image. At least, there isn’t one yet. I don’t anticipate one coming soon.

If I were to create one, it would be with Alpine Linux, built with Python 3.6.7, and would have installed Curator via

```auto
pip install elasticsearch-curator

```

It’s really not a big list of build dependencies for a Docker image.

---

<div class="post-metadata">

**Author:** ![renan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/renan/32/38627_2.png) [@renan](https://discuss.elastic.co/u/renan)\
**Post date:** [December 11, 2018, 12:33pm UTC](https://discuss.elastic.co/t/missing-few-official-docker-images/160138/3 "2018-12-11T12:33:17Z")

</div>

That's how the bobrik/curator is being built. The question is not _how_ to build but rather if it's being built by an official/trusted party. I would rather pull this image from [docker.elastic.co](http://docker.elastic.co) if possible.

---

<div class="post-metadata">

**Author:** ![jarpy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jarpy/32/51290_2.png) [@jarpy](https://discuss.elastic.co/u/jarpy)\
**Post date:** [December 12, 2018, 2:31am UTC](https://discuss.elastic.co/t/missing-few-official-docker-images/160138/4 "2018-12-12T02:31:08Z")

</div>

Journalbeat should be available with the next minor release.

> <https://github.com/elastic/beats-docker/pull/58>

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 9, 2019, 2:31am UTC](https://discuss.elastic.co/t/missing-few-official-docker-images/160138/5 "2019-01-09T02:31:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.