-
Background: We're currently using S3 as a storage for many of our files and from reading the documentation on Minio (particularly around the Gateway service), we thought we could set up Minio Gateway + Browser as a way for people to browse our S3 files, without having to create IAM roles for everyone. So as a test environment, I tried setting Minio Gateway on Docker. I followed the instructions here: https://docs.min.io/docs/minio-gateway-for-s3.html Here's the docker command I ran:
Unfortunately, this didn't seem to work. I get a 'malformed XML' error. From the Docker env:
Does anyone know what I'm doing wrong here? I feel like I'm missing something, but I can't find it in the documentation. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 8 replies
-
@jhuynh64 Not sure where you got the MINIO_REGION_NAME environment variable from. Can you check if
|
Beta Was this translation helpful? Give feedback.
-
As somebody hinted to on slack you are likely hitting a proxy/LB that writes HTML responses. |
Beta Was this translation helpful? Give feedback.
-
I'm seeing the same issue inside of a docker container. I however also see the error when i run the minio binary native on Ubuntu 20.04 API: WebListBuckets() |
Beta Was this translation helpful? Give feedback.
-
Just to post another update from me.. Our S3 buckets has a policy that only those that that are connected to our VPC (via VPN) are able to access the files. So when I tried to connect via native minio on MacOS, I was successful as I was connected through VPN. So my initial thought was that Docker for Mac has issues with VPN, I did some digging and found some bug reports to Docker for Mac with regards to VPN connection. However, after trying a few attempts, nothing worked. I then decided to So.. I'm back to square 1. Hope there are other ideas out there. |
Beta Was this translation helpful? Give feedback.
As somebody hinted to on slack you are likely hitting a proxy/LB that writes HTML responses.