Closed rwuthric closed 1 year ago
If you bind the host port with the Docker container, it should work as intended:
docker run -dp 20501:20501 -e RDK_PORT=20501 -e RDK_LIC=XXXX-XXXX-... -t robodk
Correct. The main difference compared to the documentation if the usage of robodk_path='/home/user/RoboDK/bin/RoboDK'
. Otherwise indeed works as documented.
I will update the Docker Hub read me to include the port bind. Thank you!
The
How to use this image
documentation of the RoboDK docker image says that connection to RoboDK within the image should be done asThat doesnt seem correct to me. I had to use
Is this a bug in the documentation or on my side?