We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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-entrypoint.sh: line 119: /etc/nginx/sites-enabled/default: Read-only file system
zammad-docker-compose/docker-compose.yml
Line 96 in 07936ea
/etc/nginx/sites-enabled
https://github.com/zammad/zammad/blob/74d5303cbf67c4507ccd0b78ac543f9fac533961/contrib/docker/docker-entrypoint.sh#L119 Writes the nginx config in
Is there any reason why the init container has access to the nginx config as well? This threw me off quite a bit during the search for the problem.
init
Is there any reason why the nginx container has it mounted? This seems to have been added in ffa1268 without further explanation
The text was updated successfully, but these errors were encountered:
Fixes #381 - Zammad-NGINX can not write config file due to read-only
3f6ca8d
Thanks for your report @strifel. It does not fail in the same way for me, but I agree that something is wrong with the current volume handling.
Sorry, something went wrong.
069bf2b
Fixes zammad#381 - Zammad-NGINX can not write config file due to read…
53f18a5
…-only (zammad#383)
mgruner
No branches or pull requests
Infos
Expected behavior
Actual behavior
/docker-entrypoint.sh: line 119: /etc/nginx/sites-enabled/default: Read-only file system
Steps to reproduce the behavior
Further information
zammad-docker-compose/docker-compose.yml
Line 96 in 07936ea
sets the
/etc/nginx/sites-enabled
path as read-only.https://github.com/zammad/zammad/blob/74d5303cbf67c4507ccd0b78ac543f9fac533961/contrib/docker/docker-entrypoint.sh#L119
Writes the nginx config in
Further questions
Is there any reason why the
init
container has access to the nginx config as well? This threw me off quite a bit during the search for the problem.Is there any reason why the nginx container has it mounted?
This seems to have been added in ffa1268 without further explanation
The text was updated successfully, but these errors were encountered: