ContributionsMost RecentMost LikesSolutionsRe: Ready API. Shows exception on Jenkins com.smartbear.ready.license.exception.InvalidLicenseException Regarding our use of docker, here are some specific follow-up questions which will probably be helpful for us (and others) to evaluate whether it's feasible to use the licensed version within docker containers: 1a: Have you internally tested SoapUI within docker containers, including licensing, and verified that no issues are introduced with this approach? 1b: Do you explicitly support, or explicitly do not support, it? 1c: Do you have any documentation on this? (NB: due to the popularity of docker used within test environments, such documentation would probably be useful for many people) 2. Docker containers typically run with a different IP address every time. Is this likely to cause any licensing issues? 3. Test client docker images can be newly recreated on a frequent basis. Would such frequent licence reactivations cause any problems (e.g. raise any fraud alerts)? 4. When (re)creating the test client docker image (which would likely involve a step which activates the licence), there is no capability for us to run a container from the previous docker image in order to deactivate the license before reactivation. Is this likely to cause any issues? Thanks.