cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Docker and ThingWorx license

SOLVED
Amethyst

Docker and ThingWorx license

Hello,

 

Running ThingWorx in Docker generates different device IDs every time container is restarted. We need to restart those containers frequently and automatically (several times per day). We have one ThingWorx license available, and even though we generate multiple device IDs, there is maximum one server running at a time. Is there a way to license it?

 

Regards,

Constantine

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Docker and ThingWorx license

No, it will not consume license, basically will be same license , but for different device id each time the device id is changed (this was confirmed by someone from Licensing team).

View solution in original post

7 REPLIES 7

Re: Docker and ThingWorx license

Hi,

 

In this case, what will work is to use the online licensing by updating LS_USERNAME and LS_PASSWORD with the PTC account in yml file of Docker image, to get every time a new license based on the device ID.

 

Best regards,

Raluca Edu

Re: Docker and ThingWorx license

Thanks @raluca_edu, won't it consume a new license every time a container is restarted? We have only one license and one container.

Re: Docker and ThingWorx license

No, it will not consume license, basically will be same license , but for different device id each time the device id is changed (this was confirmed by someone from Licensing team).

View solution in original post

Re: Docker and ThingWorx license

Hi Constantine,

Are you using "named" volumes for the ThingworxStorage and ThingworxPlatform folders ?
What command are you using to "restart" the container ? Restarting the container should not change its device ID.

Thanks.

Re: Docker and ThingWorx license

@smainente Sorry for causing confusion, here I use "restart" term loosely -- in fact our main use case are canary and red/black deployments in immutable infrastructure, so those containers are frequently destroyed. We also use volumeless containers in our CI pipeline, which triggers at least few times a day.

Highlighted

Re: Docker and ThingWorx license

Thanks @raluca_edu, that's what I was hoping for! Now it's time to try it in practice :)

 

/ Constantine

Re: Docker and ThingWorx license

Thanks for the clarification Constantine.

If you are not reusing the volumes, then I confirm that a new Device ID with be generated every time you spawn the container.