Using turboactivate in a docker environmentAnswered
Hi Wyatt, I am trying to set a regression for my program using a gitlab pipeline and I am having some problems when trying to activate the software in the docker container. I am getting some:
The are network adapters on the system that are disabled…
You may be familiar with those by now :). I took a look at this and https://wyday.com/limelm/help/faq/#disabled-adapters and it mentions: …and that includes all real (a.k.a. non-virtualized) network adapters attached to the computer…
So I would like to know if it is possible to activate inside a docker container or I am just waiting my time trying to run it as admin, enabling the adapters, etc.
Also took a look at this https://wyday.com/limelm/help/vm-hypervisor-licensing/
You mentioned that you should use turbofloat cause: if you let your customers activate your software on a virtual machine they can then copy that virtual machine as many times as they want.
But since we are running the activation internally, we don't have that problem, we could activate and then deactivate.
So I would like to ask what is the recommended approach for this case. If I will always get this adapter problems, or if the issue is solvable doing something in the host machine or running any other command.
Thanks!
We put close to zero effort into supporting docker. We don't deliberately break it, but we also don't spend our resources investigating it. It's a VM that's also the worst (and people inexplicably like to pretend is not a VM 🤷♂️). I'd recommend either using a better VM or configuring the docker to emulate real network adapters. Or run on real machines.
Short answer, yes, it's possible. No we're not going to write a guide on it. Google / Bing / whatever the correct incantations for the current version of docker.