Comments

8 comments

  • Avatar
    Evgeny Balashov

    Hi Sam, our team is currently working on it. We will let you know once we have it for beta testing!

  • Avatar
    Sam Buratto

    This just made my day! :)

  • Avatar
    Pieter Viljoen

    +1

    I'd love to run the server in docker on unraid instead of an ubuntu vm.

  • Avatar
    Kyle Epperson

    Hi everyone,

    Pieter and Sam, when you say "working licensing" can you describe what isn't working and how you would expect it to work if properly supported?  We want to ensure we are providing features that you actually want.

  • Avatar
    Sam Buratto

    Hey Kyle,

    I guess its a fix for the changing HWID issue, where the docker container HWID changes on a reboot.

    Not sure how this could be resolved, short of maybe attaching the license to the cloud account instead of the local NX server?

  • Avatar
    Kyle Epperson

    So you're saying you stop the docker container and when you start it back up the license is invalid?

  • Avatar
    Pieter Viljoen

    I don't know, I never got it to the point of a working container, permission problems prevented mine from starting.

    But, in a VM and Docker Container the MAC and IP is dynamic, thus they should not be used for licensing or ID'ing purposes, as they can change on every invocation.

    It is possible to fix the MAC in a VM, and with hacking it is possible in a container, but assigning a static MAC to a container is a non-standard usage, and should not be relied on.

    I do like the cloud account idea, I buy licenses, they are associated with my cloud account, I get to assign them to systems I manage. 

  • Avatar
    Kyle Epperson

    In my testing it seems to me that so long as the container is not removed it maintains licensing etc.  Though I am maintaining the database in an a volume on the host.  What I am trying to clear up is the expected operation here.  Is it expected that:

    A. The image can be saved, transferred to another computer, run as a new container with valid licensing etc.

    OR

    B. So long as the container is not removed from Docker (e.g. docker container prune) while stopped, starting up the container should continue as it was.

     

    Currently, in the testing I have been doing, B is how it works.

Please sign in to leave a comment.