Hi guys,
I have a possibly quick question. We are using Camunda Enterprise and we came accross the problem, that Camunda doesn’t find the camunda-license.txt in the resource-folder, when we are trying to deploy it as docker container. We are using Camunda 7 at the moment
Adding the license in the embedded-version works fine, also adding it via the UI, we now wanted to see if we can get a “ready-to-go” enterprise-container with the license aleady being active when deploying, so it does NOT have to be added via he UI manually.
We have tried adding it just as before into the resource-folder, but it was not recognized correctly. Is this possible? Or does it have to be different when using docker?
One thing I forgot to mention, we are not using the internal H2 but a Postgres that is running in its own container. Might this be a problem, that the DB-connection has some issue? Although it would be a little strange, because everything else regarding the DB is working
You don’t have the permission to set the key. There are some restrictions. But I’m not sure where they are relevant at startup (when the key is initially checked for).
The key file is not found. Did you set the current working directory properly for the k8s container? Where did you put the file?
We haven’t run into any issue regarding permissions. We are able to copy a file in any directory on the system. This is where we are inside of our container:
And we are not using Kubernetes, we have separate containers being put together by docker compose. This is the part for Camunda:
Based on the link previously shared in the thread, you’ll need to work out exactly which user within the container (and where that user’s home directory is) runs Camunda
It looks like you’re using the Camunda built container, so I would probably cheat a little bit, by adding a volume in your volume maps
With “permissions” I meant permissions within camunda, not within the file system. But, as I said, they should not be of importance here. As @GotnOGuts wrote, it’s crucial to know what is the current directory when the container is run. The correct location of the license file depends on that.