Fixes #381 - Zammad-NGINX can not write config file due to read-only #383
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fliebe92
approved these changes
Nov 2, 2023
floriankessler
pushed a commit
to floriankessler/zammad-docker-compose
that referenced
this pull request
Jan 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that the description in #381 is correct. The current handling of the volume
zammad-config-nginxseems to be wrong:zammad-init, but by thezammad-nginxcontainer, and thus cannot be handed over in a volume/etc/nginx/sites-enabled/is readonly, it contains a symlinkdefaultwhich points to a file that is still writable - which is why it did work on my system properlyFor me the conclusion is that we just need to remove this volume again so that the modifications are local to the
zammad-nginxcontainer.