docs(FAQ): new section for how to fix CORS issue on s3 bucket (#193)

fixes #193
This commit is contained in:
Joxit 2022-10-21 21:41:12 +02:00
parent 71df95524d
commit ee1f173355
No known key found for this signature in database
GPG Key ID: F526592B8E012263
2 changed files with 4 additions and 1 deletions

View File

@ -40,4 +40,5 @@
- Maxime Loliée [@loliee](https://github.com/loliee)
- Enrico [@Enrico204](https://github.com/Enrico204)
- [@clyvari](https://github.com/clyvari)
- Laszlo Boros [@Semmu](https://github.com/Semmu)
- Laszlo Boros [@Semmu](https://github.com/Semmu)
- [@JKDingwall](https://github.com/JKDingwall)

View File

@ -87,6 +87,8 @@ If you like my work and want to support it, don't hesitate to [sponsor me](https
- Yes you can run the container with the `nginx` user, (see [#224](https://github.com/Joxit/docker-registry-ui/issues/224)).
- Can I use the UI with a docker hub mirror and show `library/*` images ?
- Yes but it is at your own risk using two regstry servers, check the comment [#155](https://github.com/Joxit/docker-registry-ui/issues/155#issuecomment-1286052124).
- How to fix CORS issue on s3 bucket ?
- You should add a CORS Policy on your bucket, check the issue [#193](https://github.com/Joxit/docker-registry-ui/issues/193).
Need more informations ? Try my [examples](https://github.com/Joxit/docker-registry-ui/tree/main/examples) or open an issue.