Can anybody add a new startup parameter to auto install plugins in 5.0.0?

[himulawang]

That will be much convenient.

Thanks!

[willfarrell]

I'm just using the following dockerfile to wrap this image.

FROM elasticsearch:5-alpine
RUN elasticsearch-plugin install x-pack

Seems clean enough. Plus this way I don't have to wait for plugin to install every time I launch a new container.

[tianon]

Indeed, what @willfarrell said is how I'd recommend handing this too -- combine that with automated builds (https://docs.docker.com/docker-hub/builds/) and repository links (https://docs.docker.com/docker-hub/builds/#repository-links) and it's reasonably easy to have an up-to-date image built FROM this one with extra plugins installed.

[tianon]

This image is officially deprecated in favor of upstream's images (see https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html).

For more information, please see #160, docker-library/docs#842, and docker-library/docs#945.

This image has been deprecated in favor of the official elasticsearch image provided and maintained by elastic.co. The upstream images are available to pull via docker.elastic.co/elasticsearch/elasticsearch:[version] like 5.4.2. The images found here will receive no further updates once the 5.6.0 release is available upstream. Please adjust your usage accordingly.

Elastic provides open-source support for Elasticsearch via the elastic/elasticsearch GitHub repository and the Docker image via the elastic/elasticsearch-docker GitHub repository, as well as community support via its forums.

Thanks!