Open raoulbhatia opened 4 years ago
Hi,
Thank you, I will flag it as FR and try to implement it.
You could also begin using a docker-compose.override file and specify your own Dockerfile. Then you don't need to edit the org file.
You could also begin using a docker-compose.override file and specify your own Dockerfile. Then you don't need to edit the org file.
Thanks for the hint - docker-compose.override.yml
makes my life much easier! :-)
Hi, Thank you, I will flag it as FR and try to implement it.
Thanks, @andryyy. Let me know if I can be of any help. If generate_config.sh
is OK, then I would also see if/when I can find some time to implement a solution & PR for your review. Please let me know if you'd go a different route.
I'd like to configure a different set of dovecot plugins, i.e. disable zlib. The plugins are AFAICS hard-coded into the Docker container via the
docker-entrypoint.sh
script, see https://github.com/mailcow/mailcow-dockerized/blob/master/data/Dockerfiles/dovecot/docker-entrypoint.sh#L88My current solution is to use a custom
Dockerfile
that deploys a customizeddocker-entrypoint.sh
. However, this requires manual maintenance as there is no "mailcow/dovecot:latest" tag that I canFROM
in my Dockerfile and I needed to patchdocker-compose.yaml
to use my custom image (i.e.image: raoulbhatia/dovecot:1.108
). This breaks the regular update flow when the mailcow Docker image is updated.I assume there is a better solutions to my use case. For example, I can think about modifying
generate_config.sh
to put override the module by placing files into./data/conf/dovecot/
.Kindly advise if this sounds reasonable, or if you would suggest another approach.