Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using docker causes the license_checker machine_id to change #87

Open
elvintoh82 opened this issue Dec 26, 2024 · 5 comments
Open

Using docker causes the license_checker machine_id to change #87

elvintoh82 opened this issue Dec 26, 2024 · 5 comments

Comments

@elvintoh82
Copy link

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
Copy link
Member

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
Copy link
Author

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
Copy link

Hi @elvintoh82 did you happen to resolve this?

@elvintoh82
Copy link
Author

Hi @elvintoh82 did you happen to resolve this

yes I managed to resolve it in the end.

@elvintoh82
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants