# Cannot access robot interface from Docker running on Windows **URL:** \ **Category:** Report a Bug\ **Created:** [March 2, 2023, 3:42pm UTC](https://forum.universal-robots.com/t/cannot-access-robot-interface-from-docker-running-on-windows/27124 "2023-03-02T15:42:20Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![cags](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/cags/32/6304_2.png) [@cags](https://forum.universal-robots.com/u/cags)\ **Post date:** [March 2, 2023, 3:42pm UTC](https://forum.universal-robots.com/t/cannot-access-robot-interface-from-docker-running-on-windows/27124/1 "2023-03-02T15:42:20Z")
_Note:_ in case this is me doing something wrong or this is not the correct category, let me know. ### Steps to reproduce: 1. Dowload the new lastest Docker image from Universal Robots in [DockHub](https://hub.docker.com/r/universalrobots/ursim_e-series). 2. Run the specified commands to launch URSim. ```auto docker pull universalrobots/ursim_e-series docker run --rm -it universalrobots/ursim_e-series # other options for launching: docker run --rm -it -p 5900:5900 -p 6080:6080 universalrobots/ursim_e-series docker run --rm -it -e ROBOT_MODEL=UR3 universalrobots/ursim_e-series # etc... ``` ### Expected Behavior: This is from a VM Ubuntu 22.04 LTS. The UI can be accessed whether the image is launched from the terminal or VS Code. ![image](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/a/a45504ab14f4266182b319c17276f811d56cfe9f.png) ### Actual Behavior: On Windows the image can be launch from either Docker Desktop or Ubuntu 22.04 WSL, but it won’t display it. Same result when launching the image from VS Code or Docker Desktop: ![image](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/0/06e0e41ab41a441ed479f35b69c5a581382a5c5c.png) The Ubuntu subsystem is enabled in Docker Desktop with WSL 2: ![image](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/2/26d0499d0e504807cc9aa5a835a265cf5958c741.png) ### Workaround Suggestion: Apparently Windows cannot access private IP addresses in a Linux Subsystem, so I tried to launch it from a reachable IP address, but didn’t work out. So my subsystem has the IP 172.29.204.81 and Windows can ping to it. ![image](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/a/a5258f76a2ad783c59b0186da6172b9dde62107e.png) But URSim cannot be binded to it. Also tried different ports, but all failed. ```auto $ docker run --rm -it -p 172.29.204.51:5900:5900 -p 6080:6080 universalrobots/ursim_e-series docker: Error response from daemon: Ports are not available: exposing port TCP 172.29.204.51:5900 -> 0.0.0.0:0: listen tcp 172.29.204.51:5900: can't bind on the specified endpoint.ERRO[0000] error waiting for container: context canceled $ docker run --rm -it -p 172.29.204.51:5900:90000 -p 6080:90001 universalrobot s/ursim_e-series docker: Invalid containerPort: 90000. See 'docker run --help'. $ docker run --rm -it -p 172.29.204.51:50001:5900 -p 50002:6080 universalrobot s/ursim_e-series docker: Error response from daemon: Ports are not available: exposing port TCP 172.29.204.51:50001 -> 0.0.0.0:0: listen tcp 172.29.204.51:50001: can't bind on the specified endpoint. ERRO[0000] error waiting for container: context canceled ``` - What other IP addres(es) or ports can be used? - Anybody has been able to launch the interface from Windows WSL? ### Affected Version(s): URSim for e-Series 5.13 ---
**Author:** ![smarmstr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/smarmstr/32/4896_2.png) [@smarmstr](https://forum.universal-robots.com/u/smarmstr)\ **Post date:** [March 11, 2023, 10:10am UTC](https://forum.universal-robots.com/t/cannot-access-robot-interface-from-docker-running-on-windows/27124/2 "2023-03-11T10:10:22Z")
The console prompt is incorrect. Run these two commands on your Windows host machine. ```auto docker network create --subnet=192.168.56.0/24 ursim_net docker run -it -e ROBOT_MODEL=UR3e --net ursim_net --ip 192.168.56.101 -p 30002:30002 -p 30004:30004 -p 6080:6080 --name ur3e_container universalrobots/ursim_e-series ``` Afterwards, open Google Chrome and navigate to . I’ve also been able to access PolyScope via a container launched inside WSL2. For that, open a console in Windows and run `ipconfig` then look for your virtual ethernet adapter (WSL) IPv4. Afterwards, in Chrome, go to http://:6080/vnc\_auto.html . ---
**Author:** ![cags](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/cags/32/6304_2.png) [@cags](https://forum.universal-robots.com/u/cags)\ **Post date:** [March 13, 2023, 1:41pm UTC](https://forum.universal-robots.com/t/cannot-access-robot-interface-from-docker-running-on-windows/27124/3 "2023-03-13T13:41:23Z")
Yeah, that did the trick, thanks a lot! 😃 ![image](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/e/ef97a6122b91dccfca07547bc21866eba9f9e7fd.png)