-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] unexpected 403 error caused by permission setting #94
Comments
If you think we need to fix it. I am glad to give a PR. |
Hi, thank you for reporting this and providing as many details as possible. This bug has been reported sporadically in the past, and I have been unable to replicate it. Some people have experienced it in certain environments but not in others. There is surely something odd related to permissions. I won't be able to look at this for the next 10 days or so. If you have time to investigate the source of this bug in the meantime, I would really appreciate it! |
Todo for me: unscrew this, trigger the image build again. |
This should now be fixed and integrated in the (currently building) 1.25.2. I also opened #96 as a TODO for me to prevent this from happening again. Sorry for the inconvenience. In short, my Dockerfile is generated whenever a new release of nginx comes out (currently manually triggered). Changes to the Dockerfile in main are overwritten whenever an image gets built. Of course, I forgot about it 😥 |
https://github.com/apache/incubator-opendal/actions/runs/5990445081/job/16247756194?pr=2873 |
Thanks for your excellent docker image!
I am trying to use this image to setup a webdav enviroment to test OpenDAL's webdav service.
apache/opendal#2873
However, I face some problems when I want to mount a volume for
data
like this:You can check what we actually write this docker compose file in https://github.com/apache/incubator-opendal/pull/2873/files/111e694f7c036cfcc8e92649db9fce28206c8666
The webdav service gave us the
403 Forbidden
error. Log: https://github.com/apache/incubator-opendal/actions/runs/5877080995/job/15936499613?pr=2873Errors may be caused by incorrect permission settings. We try to add a Dockerfile and that solve this problem:
We seem need to create the dir and set the permission first before mark it as a volumn.
The text was updated successfully, but these errors were encountered: