-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Some configuration entries must be set as env variables ? #69
Comments
Hey @loichuder - yes, that's expected. There are some environment variables like ROOT_DIR that are used by ./runall.sh to determine which docker_compose file to invoke. E.g. if ROOT_DIR is set, it assumes that you want to use the posix HSDS: https://github.com/HDFGroup/hsds/blob/master/admin/docker/docker-compose.posix.yml. Others environment variables like AWS_ACCESS_KEY_ID are not set in config.yml because that would be a security risk to have in a text file. And finally there are some variables that are by Docker in the compose file rather than accessed by the container. E.g. "DN_RAM" sets how much memory is allotted to each DN container. Let me know if you still have questions about this. |
I see. I indeed want to use the POSIX HSDS. In this case, there is no point setting |
Right - the docker-compose.posix.yml needs ROOT_DIR to set the volume mount. |
Closing - please re-open if you have questions. |
Seeing #50, I thought that I could set all parameters in
config.yml
.I was however proven wrong when running
runall.sh
. Checks are made onROOT_DIR
andHSDS_ENDPOINT
that therefore must be set as environment variables.Is this the expected behaviour or am I missing something to use the
root_dir
andhsds_endpoint
entries in theconfig.yml
?The text was updated successfully, but these errors were encountered: