Closed zaibon closed 5 years ago
we’ll take a look @zaibon
@zaibon can you paste the command line you're using to start Mint, (ofcourse, remove any sensitive info)
@nitisht
docker run -e SERVER_ENDPOINT={url} -e ACCESS_KEY={key} -e SECRET_KEY={secret} -e ENABLE_HTTPS=1 minio/mint
can you try docker run -e SERVER_ENDPOINT={url} -e ACCESS_KEY={key} -e SECRET_KEY={secret} -e ENABLE_HTTPS=1 minio/mint mc
mc test works ok
(1/1) Running mc tests ... done in 3 minutes and 58 seconds
All tests ran successfully
In that case, this looks like something to do with aws-sdk-go
tests that we have. Can you try all other SDKs in mint,
docker run -e SERVER_ENDPOINT={url} -e ACCESS_KEY={key} -e SECRET_KEY={secret} -e ENABLE_HTTPS=1 minio/mint mc awscli aws-sdk-php aws-sdk-ruby aws-sdk-java minio-go minio-java minio-js minio-py minio-dotnet s3cmd
@zaibon closing this due to no response, feel free to reopen when you have more info
I've been working on a project where I implement the gateway interface of minio to reach my backend. To make sure I implemented everything properly I tried to run the mint test suite on my minio implementation.
I discovered some strange behaviors:
ENABLE_HTTPS=0
Here is the logs of mint when running against traefik with auto https:
What could be the reason of such a behavior ?