Ask a Question

Fixed User licenses cannot be used on virtual machines or with docker containers

Regular Visitor

Fixed User licenses cannot be used on virtual machines or with docker containers

I am using a fixed license for a ReadyApi installation on a VM, without any problem so far.

I came across on recent changes on Ready Api documentation here,

where it says that "Fixed User licenses cannot be used on virtual machines or with docker containers."


Will this technically prevent me working with a fixed license on a VM from now on?

What problem may I come across by using a fixed license on a VM?

And how this is interpreted since the majority of IT , nowadays, works with virtual machines and docker containers anymore?



We are potentially facing the same dilemma.
We are currently using a fixed license on our VM which runs our daily CI/CD tests without any issues.
I am in the process of evaluating an upgrade to a current release, but do not want to jeopardize losing the benefit of those tests running daily if we must / be required to have a floating license for a VM.

If you are moving to the ID based license, this link explains how to use the accessKey in the testrunner script executed on the VM. 

We are going to give this a shot later today and will let you know if that is a viable option.

Occasional Contributor

Hi, @sdeevers 


Would you mind to share the results of using ID based license on VM?



@ihorstep  - Unfortunately, we have been put on hold till our IT department can determine the "best" user ID we should use for that VM instance (the associated email will need to be public facing to receive the link to create the SB License server account).  Once IT lets us know, we will update our CI/CD plans to use the associated "accessKey" information and let you know if all is fine.

Showing results for 
Search instead for 
Did you mean: