Using docker causes the license_checker machine_id to change

[elvintoh82]

I'm trying to use anygrasp by setting up the environment in a dockerfile.

But I realise that the the machine_id that is generated by license_checker -f fluctuates if I make some slight changes to my dockerfile or when I start the containers using docker compose (especially if I change the static ip of that particular container).

The motivation why I want to do things in docker is because the setting up of the environment from minkowski engine, graspnetapi and pointnet2 is a very complicated process that I do not want to install the packages (and their dependencies) on my actual system. I would rather contain those inside a dockerfile for consistency.

The issue appears when I created a dockerfile that can work and even have a machine_id that I applied in the license form. Unfortunately, after I made some changes to the dockerfile, the machine_id has now been changed. Further experimenting also made me realise that if I use a different static ip for the container, the machine_id changes again.

My concern is that if i I reapply for the license form again, it may appear that I am trying to circumvent the licensing, and it still might not work because the machine_id might change again.

Could someone advise how you overcome this issue of a changing machine_id that results from setting things up in a dockerfile?

To clarify, I'm not trying to distribute or anything, I'm simply trying to set up the environment using a dockerfile for consistency, especially considering that the various depencencies across different platform (ubu 22, 20, 18) can cause the installation to vary quite a bit.

[Fang-Haoshu]

Hi, I would suggest using a conda environment, it's much more lightweight and won't mess the environment. We are using conda on our machine

[elvintoh82]

Hi, I would suggest using a conda environment, it's much more lightweight and won't mess the environment. We are using conda on our machine

Thanks Fang-Haoshu, as my test includes some variations of ROS and moveit and other packages (not necessarily involving pip installing stuff), that added a layer of complexity in setting up the environment. As a result, docker continues to be my main basis of setting things up.

[adithyamurali]

Hi @elvintoh82 did you happen to resolve this?

[elvintoh82]

Hi @elvintoh82 did you happen to resolve this

yes I managed to resolve it in the end.

[elvintoh82]

It was closely tagged to the mac address although I'm not sure if there might be other parameters/names that could affect the feature_id too or not

[ge79puv]

@elvintoh82 @Fang-Haoshu Hi, if I keep using the same docker container, will the feature id change sometimes?

[Moni9612]

@elvintoh82 , im having the same problem I got the license by providing my machine's feature ID. But later due to the same complexities which u mentioned, I thought of moving with docker as well. Can u please help explain how u resolved the license issue

[ma8sa]

@elvintoh82 , Hey I too am having the same issue, I using docker to help with the different requirements for ROS , I orignally created the license on a different image but now the project has moved to a newer image and license is no longer valid. I would be of great help if you could share how you resolved it