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
Start container with env var S3_STYLE set to "path" and S3_BUCKET_NAME set to "mybucket"
View logs
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/00-check-for-required-env.sh
S3 Backend Environment
Access Key ID: <omitted>
Origin: http://mybucket.service.namespace.svc.cluster.local:9000
Describe the bug
Logs generated at https://github.com/nginxinc/nginx-s3-gateway/blob/main/common/docker-entrypoint.d/00-check-for-required-env.sh#L127 do not accurately reflect the server path used during runtime. This is quite misleading on first glance. Program logic accounts for
S3_STYLE
https://github.com/nginxinc/nginx-s3-gateway/blob/main/common/docker-entrypoint.sh#L86-L95 and seems to set the address correctly for nginx, but this does not match the logs I mentioned above.To reproduce
Steps to reproduce the behavior:
S3_STYLE
set to "path" andS3_BUCKET_NAME
set to "mybucket"Origin
Expected behavior
When
S3_STYLE
is set to "path", the line beginning withOrigin
should display an origin that does not include the bucket name. ie. http://service.namespace.svc.cluster.local:9000Your environment
Thanks!
The text was updated successfully, but these errors were encountered: