Hi Ivor,
>> "But are you aware of any issues or potential problems that could arise from TA itself, as well as from within my app, when executing from inside a docker container?"
Within sandboxes or virtual machines you should really use TurboFloat because the "hardware" of the computer can and does change. Plus the "hardware" can be cloned bit-for-bit.
More about this here: https://wyday.com/limelm/help/vm-hypervisor-licensing/
More about TurboFloat here: https://wyday.com/limelm/help/using-turbofloat/
>> "2) Do I understand correctly that a request to verify a license only returns a YES or NO?"
No, absolutely not. There are crappy licensing solutions that do that: https://wyday.com/limelm/features/why/#hardware-locked-descr
Our licensing is actually well designed.
>> "A license that also contains parameterized execution details and / or limits, in other words."
I believe custom license fields is what you're looking for: https://wyday.com/limelm/help/license-features/
>> "3) Any plans to allow for a TA for floating licenses to exist on a limeLM server itself instead of local to the client's network?"
We've thought about it. Can you explain your use-case more? Would you want this so that customers wouldn't have to install the TurboFloat Server somewhere on their network? Or are the additional reasons?