Plugins folder that is not shared with installer for use in docker
Answered
The plugins folder is located under bin and contains already installed plugins, and adding custom plugins mixes them with the already installed plugins.
In docker this makes it impossible to create an image that uses plugins, as the image itself needs to be updated to mix the custom plugin with the base image.
Is there a different path where plugins can be loaded from that is external and unpopulated to the pre-installed plugins, or can such a feature be added?
E.g. can I mount a sub-directory under bin/plugins e.g. bin/plugins/foo that is mapped to an external volume?
-
Hi Pieter Viljoen,
Thanks for your suggestions and raising these good questions. Unfortunately, at the moment this has not yet been a supported way to configure the system plugins.
The current plugin mechanism is designed for the user can easily add/remove the plugin on a running system, so we suggest/provide the user a "copy-paste" way to add/remove the plugins.
I can understand there might be some extra work and effort would be required in your use case, but fortunately it is not the show-stopper. Anyways, thanks for pointing this out and raise the requests again. We will consider about your advice and suggestions.
Appreciate!
0 -
On docker this is a "show-stopper", as the bin folder is replaced whenever the container image is updated, the plugins folder must be in a mounted volume if it is to be persisted across image updates.
0 -
Hi Pieter Viljoen,
Thanks for your suggestions. At the moment, we think this is something can be workaround by replacing the proper folder, and this is something on the scope of the docker/system.
Your suggestions are great and we would consider to improve the experience in the future version, but at the moment, it is likely you would need to manually configure the plugin after any installation which is the expected behavior for most of the users who has the capabilities to configure the system.
Thanks.
0 -
To my knowledge there is no way to merge the contents of a mounted volume with content in the image, i.e. the installer writes its own plugins, so if a volume is mounted it will hide the installed plugins.
If I misunderstood, kindly provide an example of how to mount a volume with user supplied plugins that is used in the docker image without overwriting the installed plugins?
As for it being the expected behavior, that is contrary to how docker works, and not how docker is deployed in productions.
0
Please sign in to leave a comment.
Comments
4 comments