17 ms·
After 1 google search: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html https://www.elastic.co/guide/en/elasticsearch/reference/curr.
by jillesvangurp 7y ago
After 1 google search: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html https://www.elastic.co/guide/en/elasticsearch/reference/curr...
It includes a deep link straight into their repository right at the top: https://github.com/elastic/elasticsearch/tree/7.1/distribution/docker https://github.com/elastic/elasticsearch/tree/7.1/distributi...
In short, their Docker build process is part of the elasticsearch repository. So, it's actually part of their normal build process and not something that happens with a separate build in some different repository. Personally, I think this is a good practice.
That's for both the OSS and non OSS images. They produce these with every build. And they probably test them too, which I think is the responsible thing to do and something I'd expect from them.
They use gradle to build their docker images from a Docker file (https://github.com/elastic/elasticsearch/blob/7.1/distribution/docker/src/docker/Dockerfile https://github.com/elastic/elasticsearch/blob/7.1/distributi...) that essentially untars the tar ball produced by their build. This looks pretty straightforward and free of magic steps.
So, read the source. It's all there. You can build from source or do your own thing. A variant of their Docker file where you just wget their tar ball shouldn't be that hard to do.