-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrating the plugin into the "Camunda Docker Run" image #16
Comments
@MrRickwi I recall that the run image has everything baked into JAR-files and it does not support reading plugins out of those JARs. I believe that you should be able to adapt the examples in the forum https://forum.camunda.org/t/minimal-cockpit-history-plugins-for-camunda-7-14-0/24651/17 to get the plugin files into the image. You should not need to add camunda-cockpit-ui.js, because it should be already there. |
That solved the problem: My final minimal Dockerfile for Camunda Run looks now like this:
I think it would help to include this in README.md... Thanks a lot! |
I add link from README to this issue 👼 |
Same thing, into a single Dockerfile:
I love your project, it's fabulous !!! |
Neither of theses solutions worked for me on version 7.16 To get the plugin installed:
dockerfile:
Note: For COPY to work files need to be copied from the same directory as the dockerfile i.e. root I also found watching this video helpful to give some more context/insight into plugin development: Thanks for the plugin it is awesome! great work :) |
I can confirm that plugin Dockerfile are working fine on 7.19
|
Works also with 7.20.0. |
It also works with 7.21.0.
|
Hi, is there any way to integrate the plugin into the "Camunda Docker Run" image which can be found here:
docker pull camunda/camunda-bpm-platform:run-7.15.0
I tried it with a Dockerfile like this:
with no success. Any hints? Interesting part: The file camunda-cockpit-ui.js is missing in the run image, so I suppose this image is stripped down not to support any plugins. Right?
The text was updated successfully, but these errors were encountered: