It seems that the description in #381 is correct. The current handling of the volume zammad-config-nginx seems to be wrong:
the nginx config does not get written by the zammad-init, but by the zammad-nginx container, and thus cannot be handed over in a volume
even if /etc/nginx/sites-enabled/ is readonly, it contains a symlink default which points to a file that is still writable - which is why it did work on my system properly
For me the conclusion is that we just need to remove this volume again so that the modifications are local to the zammad-nginx container.
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.