Having deployed our Cryptlex-containing app in BitBucket pipes so as to perform DevOps on our project, we noticed that VM detection of these app instances running in docker containers doesn’t detect such a situation. Although we set a VM detection and forbidding in the license policy, Cryptlex doesn’t preclude the code from being executed in these docker containers. This seems special since we can’t reproduce the issue with our own docker images or VMs.
OK, we understand our local test was wrong since we were running docker inside a VM, Cryptlex blocking, and us thinking that AllowVm=false would block docker execution. Is there anyway we can prevent this or is the 200$/month floating server our only option to control the execution in docker images with your technology?
Digging a bit further, I can’t find a way to offer my customers a trial period with a trial policy that prevents them from running the trial inside docker. Then they would simply rerun a docker of the trial app before the end of the trial and have a continuous use of the app for free. Or is there something, most probably, that we don’t understand correctly.
OK, trying this this morning, I can’t find the checkbox with “Allow Container Activation” when creating a Trial Policy. How do I create this policy? Thank you
Hi Adnan,
I haven’t been able to find out how to set “ALLOW CONTAINER ACTIVATION” to false from the dashboard. Am i missing something?
Thanks in advance,
Patrice
The option “ALLOW CONTAINER ACTIVATION” is not exposed in the dashboard. You can only do it using the web API. Below is the link which can help you know how you can do it using the web API: