-
Notifications
You must be signed in to change notification settings - Fork 49
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
PermissionError: [Errno 13] Permission denied: '/public/media' #56
Comments
Happy to merge PRs fixing this problem! As the pretalx docker image is community maintained, I won't have time to look into this myself. |
I was not able to reproduce the issue. Could you please share more details about your setup? Are you using docker/docker-compose? Do you use docker volumes? Did you follow the production instructions? |
@Zaczero I only cloned it and ran |
Weird, because I just set up pretalx-docker for the first time in probably five years, literally only ran Would be nice if somebody could either provide better setup instructions or add the |
The problem seems to be that currently there is no pre-built |
There is no new image being released, because the GitHub action for a release ran into a timeout after six hours of … not much happening (cf). I'll re-run the job, but if that doesn't change anything, somebody will have to fix the build or people will just have to build the image locally. |
Same issue for me. PermissionError: [Errno 13] Permission denied: '/public/media' Thanks in advance. |
Have faced the same problem (ans still have some open). I made a PR
@rixx Happy to make a PR to hopefully imporve UX, as it took me hours to find that out.. Not sure to fix all the problems people facing in this issue but at least it give some hints! #60 (Btw, still facing some issues with pretalx ignoring static path and imho the main docu could also improved, but thats in an other issue in the main repo) |
pretalx is open source and happy for contributions. Apart from that, it's mostly developed (and documented, and run, …) by me on my own, and the documentation (as well as every other part of the project) being imperfect just comes with the fact that I have limited time and attention. Apologies that it took you hours to find out how to run pretalx – this is probably where I should remind people that there's also the offer of hosted pretalx and/or a support contract for immediate help with problems like that. |
A workaround I did was
sudo docker exec --user 0 -ti pretalx pretalx init
, but I hadn't yet verified whether it solves the problemThe text was updated successfully, but these errors were encountered: