# Feature request: Could the docker image allow more customization so that we don't have to keep making custom images based on this one

**URL:** <https://discuss.elastic.co/t/feature-request-could-the-docker-image-allow-more-customization-so-that-we-dont-have-to-keep-making-custom-images-based-on-this-one/145210>\
**Category:** Elasticsearch\
**Created:** [August 20, 2018, 4:56pm UTC](https://discuss.elastic.co/t/feature-request-could-the-docker-image-allow-more-customization-so-that-we-dont-have-to-keep-making-custom-images-based-on-this-one/145210 "2018-08-20T16:56:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yokhahn](https://avatars.discourse-cdn.com/v4/letter/y/8e7dd6/32.png) [@yokhahn](https://discuss.elastic.co/u/yokhahn)\
**Post date:** [August 20, 2018, 4:56pm UTC](https://discuss.elastic.co/t/feature-request-could-the-docker-image-allow-more-customization-so-that-we-dont-have-to-keep-making-custom-images-based-on-this-one/145210/1 "2018-08-20T16:56:55Z")

</div>

I'm trying to use the official docker image, via a helm chart. One of the problems that I keep running into is that the architecture of the current image requires customizing the docker image to make many configurations work (inheriting from the official image). I believe small changes to the image would prevent the need for this extra work.

For example, instead of requiring an overriding of the entry point script and then daisy chaining onto it in order to install the s3 repository plugin. Why not allow the original entrypoint script to check for the existence of a script at a certain path (e.g. /custom/my\_custom\_start)? That way customization could be done with a volume mount instead of re-creating the image.

This could also allow things like kubernetes secrets to be transferred to a keystore via a custom mount for the script and a secrets mount as well.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 20, 2018, 9:43pm UTC](https://discuss.elastic.co/t/feature-request-could-the-docker-image-allow-more-customization-so-that-we-dont-have-to-keep-making-custom-images-based-on-this-one/145210/2 "2018-08-20T21:43:50Z")

</div>

It'd be great if you could raise a feature request for this right here - [https://github.com/elastic/elasticsearch-docker](https://github.com/elastic/elasticsearch-docker)

---

<div class="post-metadata">

**Author:** ![yokhahn](https://avatars.discourse-cdn.com/v4/letter/y/8e7dd6/32.png) [@yokhahn](https://discuss.elastic.co/u/yokhahn)\
**Post date:** [August 22, 2018, 4:34pm UTC](https://discuss.elastic.co/t/feature-request-could-the-docker-image-allow-more-customization-so-that-we-dont-have-to-keep-making-custom-images-based-on-this-one/145210/3 "2018-08-22T16:34:38Z")

</div>

@warkolm

I've put in a feature request here:  
[https://github.com/elastic/elasticsearch-docker/issues/189](https://github.com/elastic/elasticsearch-docker/issues/189)

And proposed my own patch to add the feature here:  
[https://github.com/elastic/elasticsearch-docker/pull/190](https://github.com/elastic/elasticsearch-docker/pull/190)

---

<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:** [September 19, 2018, 4:34pm UTC](https://discuss.elastic.co/t/feature-request-could-the-docker-image-allow-more-customization-so-that-we-dont-have-to-keep-making-custom-images-based-on-this-one/145210/4 "2018-09-19T16:34:39Z")

</div>

Closed on September 19, 2018, 4:34pm UTC

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