You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently trying to start the official Solr container with a mounted path instead of a docker volume.
I am getting an error on startup that solr.xml and zoo.cfg are not writeable.
It seems that the issue is that those files are created with root:root and the owner is not changed correctly.
If I change the owner/mod o+rwx of both files, the container starts without an issue and more directories are created along them with the correct 1000:1000 UID/GID.
I am not sure what the issue is, it seems to me that this is done inside the Solr Dockerfile
But maybe it is not possible to use a mounted path with the current Dockerfile setup?
I would prefer a file over volume because it is not possible to move normal docker volumes outside of the root file system, e.g. to a network storage.
Issue Reproduction
Modified ansible part (master and slave are identical):
- name: Start Solr child containerdocker_container:
name: solr-slaveimage: "{{ solr_image_prefix }}/{{ solr_image_repository }}:{{ solr_image_tag }}"pull: "{{ solr_image_pull }}"command:
- solr
- -f
- "-Dmaster.enable=true"
- "-Dslave.enable=true"
- "-Dslave.masterUrl=http://solr-master:8983/solr"
- "-Dslave.pollInterval={{ solr_slave_poll_interval }}"# This is the Solr instance used for queries, so we need to enable shards# However we want to use a whitelist so that only queries for configured shards are allowed
- "-Dsolr.shardsWhitelist={{ solr_shards_whitelist | join(',') }}"detach: yesrestart_policy: unless-stoppedexposed_ports:
- "8983"networks:
- name: esgfnetworks_cli_compatible: yesvolumes: ["/some-mount/solr-slave/data:/var/solr/data:rw"]state: startedrecreate: yes
First container start:
-rw-------. 1 root root 2180 Mar 24 2019 solr.xml
Changing permission:
sudo chown 1000:1000 solr.xml
Second container start:
-rw-------. 1 esgf esgf 2180 Mar 24 2019 solr.xml
-rw-------. 1 root root 975 Feb 21 2019 zoo.cfg
I am currently trying to start the official Solr container with a mounted path instead of a docker volume.
I am getting an error on startup that solr.xml and zoo.cfg are not writeable.
It seems that the issue is that those files are created with root:root and the owner is not changed correctly.
If I change the owner/mod o+rwx of both files, the container starts without an issue and more directories are created along them with the correct 1000:1000 UID/GID.
I am not sure what the issue is, it seems to me that this is done inside the Solr Dockerfile
But maybe it is not possible to use a mounted path with the current Dockerfile setup?
I would prefer a file over volume because it is not possible to move normal docker volumes outside of the root file system, e.g. to a network storage.
Issue Reproduction
Modified ansible part (master and slave are identical):
First container start:
Changing permission:
Second container start:
Changing permission again:
Third and final container start:
The text was updated successfully, but these errors were encountered: