Closed cultpony closed 3 years ago
basisbit
commented
3 years ago Before elastic is started again, ensure that the permissions for the ./local-data/elastic folder are 777 so elastic can spawn the proper folders inside.
Why would that be necessary to do? Only the docker container would have created that folder, so there should be no need to change anything there. If however there is some need to change permissions, then that should probably be added to the container build script?
cultpony
commented
3 years ago Why would that be necessary to do? Only the docker container would have created that folder, so there should be no need to change anything there. If however there is some need to change permissions, then that should probably be added to the container build script?
Only for the first run. The issue is that elastic doesn't run as root, there is no init script that could fix it, since the script would run as non-root as well. The folder ./local-data/elastic is created by docker-compose on first startup with local user permissions, which isn't the same as the container user. Once the permissions are changed, this shouldn't be necessary ever again.
Before you begin
I understand my contributions may be rejected for any reason
I understand my contributions are for the benefit of this imageboard software
I understand my contributions are licensed under the GNU AGPLv3
[x] I understand all of the above
Elastic mounted the wrong folder into the FS: https://www.elastic.co/guide/en/elasticsearch/reference/7.8/docker.html
Before elastic is started again, ensure that the permissions for the ./local-data/elastic folder are 777 so elastic can spawn the proper folders inside.