Pulling from Minio/S3 is broken

cityofcapetown / docker_wui

Minimalist, Nginx-based image for serving up content. Intention is for it to be used to serve up static web content.

MIT License

0 stars 0 forks source link

Pulling from Minio/S3 is broken #3

Closed Gordonei closed 5 years ago

Gordonei commented 5 years ago

Looks like the XML parser is breaking on the response from Minio/S3.

Place to start would be this line, which parses the response..

Gordonei commented 5 years ago

Reproduction of the problem:

$ sudo docker exec -it metadata-registry-inspector bash -c /refresh.sh
2019-05-24T17:59:35+02:00 Refreshing content

no element found at line 2, column 0, byte 1:

^
 at /usr/lib/x86_64-linux-gnu/perl5/5.24/XML/Parser.pm line 187.
2019-05-24T17:59:39+02:00 No more content found at 'https://172.29.100.54:8001/metadata-registry-inspector'
2019-05-24T17:59:39+02:00 Finished refreshing content

Gordonei commented 5 years ago

Turns out it was because the CONTENT_URL was malformed. Should probably add more explicit error handling for that.

Some sort of preliminary check to see whether the response is in fact a minio/S3 bucket list.