Alpine-based s3fs client: mount from container, make available to other containers
BSD 3-Clause "New" or "Revised" License
173
stars
62
forks
source link
docker-entrypoint.sh: reading AWS_S3_SECRET_ACCESS_KEY variable from file not working, request for reading variable from file for AWS_S3_ACCESS_KEY_ID #50
Question 1:
In docker-entrypoint.sh should:
AWS_S3_SECRET_ACCESS_KEY=$(read -r "${AWS_S3_SECRET_ACCESS_KEY_FILE}")
on line 66 not be:
read -r AWS_S3_SECRET_ACCESS_KEY < "${AWS_S3_SECRET_ACCESS_KEY_FILE}"
to be able to work properly (i.e. read from the file path indicated with AWS_S3_SECRET_ACCESS_KEY_FILE and store in variable AWS_S3_SECRET_ACCESS_KEY)?
Question 2:
Could this same behavior (i.e. reading from file) be implemented for:
AWS_S3_ACCESS_KEY_ID
?
Question 1: In docker-entrypoint.sh should: AWS_S3_SECRET_ACCESS_KEY=$(read -r "${AWS_S3_SECRET_ACCESS_KEY_FILE}") on line 66 not be: read -r AWS_S3_SECRET_ACCESS_KEY < "${AWS_S3_SECRET_ACCESS_KEY_FILE}" to be able to work properly (i.e. read from the file path indicated with AWS_S3_SECRET_ACCESS_KEY_FILE and store in variable AWS_S3_SECRET_ACCESS_KEY)?
Question 2: Could this same behavior (i.e. reading from file) be implemented for: AWS_S3_ACCESS_KEY_ID ?