Skip to content
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

Docker container start-up fails with permission denied error #1911

Closed
2 tasks done
RobinWeitzel opened this issue Jul 26, 2023 · 3 comments
Closed
2 tasks done

Docker container start-up fails with permission denied error #1911

RobinWeitzel opened this issue Jul 26, 2023 · 3 comments
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.

Comments

@RobinWeitzel
Copy link

Describe the issue

Starting a new weblate server following the instructions here fails with a
"permission denied" error.
This occurs on multiple different systems and both with older and newer Weblate versions (though the error is different between v4.17 and v4.18).
All systems are RHEL systems.

I saw a related issue #1831 but the suggestions to use the "bleeding" version did not fix it either.

Version I tested:
edge
bleeing
v4.18
v4.17

Logging into the container while it is running and checking the permissions of the /tmp/nginx folder gives me: "drwxr-x---, 2 root root 40 Jul 26 09:47 nginx"

I also tried turning "read_only" in the docker-compose file to "false".

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

Download docker-compose file from GitHub: https://github.com/WeblateOrg/docker-compose.git
Set "WEBLATE_SITE_DOMAIN" in environment file
Run "sudo docker-compose up" in the directory

Wait for the DB & Redis to start up.
The Web container starts up and performs migrations.
After that if fails (see screenshots).

Expected behavior

Container is able to write to /tmp/nginx and starts up normally

Screenshots

error_4 18
error_4 17

Exception traceback

No response

Additional context

I have an old server where version 4.14 is running on. That version works but if I go to that server and try to launch version 17 or 18 it fails with the above errors as well.

@nijel
Copy link
Member

nijel commented Jul 27, 2023

You either need /tmp volume or disabling read_only for weblate container.

@nijel nijel added the question This is more a question for the support than an issue. label Jul 29, 2023
@github-actions
Copy link

This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks!

In case your question is already answered, making a donation is the right way to say thank you!

@github-actions
Copy link

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Aug 13, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants