Closed nupplaphil closed 4 years ago
Ugh. Do you know the feeling of regret when touching a specific code path, when afterwards all the side effects of this small change come creeping in? :sweat_smile:
create a new Dockerfile like:
That is actually not necessary. There is a make target called build-webapp-plugins
that will create a WebApp image with plugins pre-installed.
But even if these packages were installed before, based on prior tickets in this repo, I would guess they were never configured through environment variables?
I have tinkered with it a bit and the best solution I could come up with so far is included as an example in the linked pr. Essentially you need to enhance the Dockerfile where you install your additional selection of plugins with the snippet that can be found at the end of https://github.com/zokradonh/kopano-docker/blob/5ba557c3264c357a1f0953b7bb68f9bef044e5f1/webapp/Dockerfile.plugins
.. or run your container not read only (but I would opt for enhancing your Dockerfile).
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Describe the bug In case extending the kopano_webapp image with plugins, all plugins with config files are making the start of webap as a read-only container failing, like:
To Reproduce
install Kopano WebApp and refresh ca-certificates
hadolint ignore=SC2129
RUN \
install
docker-compose build
docker-compose up kopano_webapp
Expected behavior Startup without errors, so the plugins are working even with read-only containers.