Unable to Uninstall X-Pack with elasticsearch:5.2.2 Docker Image #36
Comments
|
Hi, I had the same problem and I fixed it with the following Dockerfile : I found this solution here : docker-library/elasticsearch#141 |
|
Hello, Please see the suggestion here: #35 (comment) for a workaround. We identified an issue with the |
|
@dliappis While this issue is closed, in the latest Elasticsearch 5.4.0, while you can now remove x-pack with the remove command, it still causes the same file system errors the next time you start the container for elasticsearch. |
|
@tylerjharden I've reopened this issue and thanks for reporting it. |
|
@tylerjharden For ref, I tried to replicate (unsuccessfully) building a customized image using the following simple Dockerfile: Then built a customized image using: Which ended up running successfully: Looking forward to your replication steps. |
|
So I was able to fix the issue, but my fix exposes that what is declared fixed (fallback to non-atomic removal for non top-layer file systems), is not working as expected. The version of the Dockerfile we had in use that prompted this issue is as follows: On my own, after tracing several issues around where the root cause (in the Linux kernel) was described in a docker hub GitHub issue that I am now having a hard time finding, it was stated that you can circumvent this by ensuring that the command is run in the top layer of the docker image, and by doing so, I am able to get it working: So the reason your replication attempt was unsuccessful is because you perform no layers after the x-pack removal, add something simple that touches file system (or maybe even any layer period, I did not try to make it fail multiple ways since it is fixed for us using this 'hack'), but who knows. |
|
@tylerjharden Thank you very much for the detailed steps. This will help us add steps to the current x-pack plugin removal acceptance test. I did try the However, those layering problems do occasionally surface depending on the storage driver. I'd definitely be interested to get an output of your [1] $ tree
.
├── config
│ ├── elasticsearch.yml
│ ├── jvm.options
│ └── log4j2.properties
├── Dockerfile
└── docker-healthcheck
1 directory, 5 files$ cat Dockerfile
FROM docker.elastic.co/elasticsearch/elasticsearch:5.4.0
COPY docker-healthcheck /usr/local/bin/docker-healthcheck
COPY config /usr/share/elasticsearch/config
RUN elasticsearch-plugin remove x-pack
# cleanup unused modules to slim image
RUN rm -rf modules/aggs-matrix-stats
RUN rm -rf modules/ingest-common
RUN rm -rf modules/lang-expression
RUN rm -rf modules/lang-groovy
RUN rm -rf modules/lang-mustache
RUN rm -rf modules/percolator
RUN rm -rf modules/transport-netty3 |
|
This occurs using Docker for Mac on MacOS Sierra 10.12.4 output of docker info: |
|
If someone needs to uninstall x-pack from docker-compose, this article will help: https://blog.codeship.com/orchestrate-containers-for-development-with-docker-compose/ |
|
ElasticSearch now has oss versions of their docker images (without xpack). They do not however, have them listed on their docker images page: https://www.docker.elastic.co/ However, you can add -oss to their links (worked for the version 6 ones) it gives an image without xpack:
|
All images can be seen by expanding the listing as shown below:
Just hover over the yellow arrow and click on it:
|
When I try to remove x-pack in the official image, I get the following error.
Dockerfile
FROM docker.elastic.co/elasticsearch/elasticsearch:5.2.2
.....
I created a repository to built into docker hub to demonstrate this problem.
GitHub Repo: https://github.com/frekele/docker-elasticsearch
Docker Hub: https://hub.docker.com/r/frekele/elasticsearch/
You can see inside the build log the error:
Related Issues with deprecated repository:
The text was updated successfully, but these errors were encountered: