Well, you’re going to need to have to do one of three things:
Live with just the in-memory H2 database and risk losing data if the container crashes
Connect to a standard, external database instance
Configure docker to provide a persistent storage volume somewhere and then either add a database like MySQL to the container, or configure the H2 database to use local persistence.
I have never done any of the above as I don’t run Camunda in docker. But folks I work with are running it in Kubernetes using SpringBoot, etc., etc., etc. and these are the options we arrived at for them. They chose to connect to a standalone external database.
one with camunda engine embedded in a SpringBoot app
and one with camunda standalone-app (cockpit-tasklist-admin)
Off-course I’m saying one for each here but in reality, I meant set of pods: a mysql (master + slave pods ), several camunda engine and several camunda stand-alone app.
I was able to deploy a container on a kubernetes cluster as well, but getting the same error when trying to deploy it in openshift. Anybody was able to deploy camunda on openshift?
Configure database
failed to load external entity “/camunda/conf/server.xml”
[/quote]