yikyo
yikyo
Using a custom dockerfile can make it work properly. ``` dockerfile FROM efrecon/s3fs:1.94 RUN sed -i \ -e '69s/.*/ AWS_S3_ACCESS_KEY_ID=$(cat "${AWS_S3_ACCESS_KEY_ID_FILE}")/' \ -e '75s/.*/ AWS_S3_SECRET_ACCESS_KEY=$(cat "${AWS_S3_SECRET_ACCESS_KEY_FILE}")/' \ /usr/local/bin/docker-entrypoint.sh ```
I used cat to replace the read command and it worked normally, so it's not a permissions issue, right? [https://github.com/efrecon/docker-s3fs-client/issues/58#issuecomment-2391565851](url)
> I am unable to reproduce this. Can you set `S3FS_DEBUG` to `1` and see if s3fs itself reports a problem? Unable to start, no logs