Port 9000 refused to connect

[NoChizPlz]

Platform Ex 2 ultra

Application Docker

Describe the bug After i install docker i click configure and leads me to port 9000 but it refused to connect

[D-stefaang]

See #49

[D-stefaang]

It could also be that it's an issue with the networking layer in docker. https://community.wd.com/t/package-docker-v18-03-1-ce-for-wd-my-cloud/222305/71

[D-stefaang]

https://github.com/WDCommunity/wdpksrc/pull/58

[Nitram91]

On my WD-MyCloud EX 2 Ultra the Release MyCloudEX2Ultra_docker_19.03.8.bin doesnt work. Port 9000 = connection refused. I looked in the File /mnt/HD/HD_a2/Nas_Prog/docker/daemon.sh Line 211 is ${DOCKERD} -D >> /var/lib/docker/docker.log 2>&1 & and not ${DOCKERD} -D --ip-masq=true >> /var/lib/docker/docker.log 2>&1 & like in the Source. I changed it and restartet the Nas, but it doesnt work...

Its only working, if i bind the container to the Host Network with the Command "docker run -d --network="host" ..." like https://community.wd.com/t/package-docker-v18-03-1-ce-for-wd-my-cloud/222305/71

Has somebody any Ideas?

[Myron-S]

Just a note. After I upgraded to OS5 portainer started to work, but I didn't install the now separate Twonky app, but I do have Plex Server installed and the DNLA service on the Plex Server is enabled.

[mrbscott]

I installed 19.03.08 via the bin file then replaced the docker contents with 20.10.7 and ran a modified version of update_portainer.sh with a different port. When I tried to start the portainer container I get the following error: Error response from daemon: runtime "io.containerd.runc.v2" binary not installed "containerd-shim-runc-v2": file does not exist: unknown

[JediNite]

@mrbscott.

Check the contents of the following :

root@WDMyCloudEX4100 docker-20.10.7 # pwd
/mnt/HD/HD_a2/Nas_Prog/docker/docker
root@WDMyCloudEX4100 docker-20.10.7 # ls -al
drwxr-xr-x    2 root     root          4096 Jun 13 15:59 .
drwxrwxrwx    8 root     root          4096 Jun 13 15:59 ..
-rwxr-xr-x    1 root     root      34624276 Jun 13 15:59 containerd
-rwxr-xr-x    1 root     root       6356992 Jun 13 15:59 containerd-shim
-rwxr-xr-x    1 root     root       8585216 Jun 13 15:59 containerd-shim-runc-v2
-rwxr-xr-x    1 root     root      18677188 Jun 13 15:59 ctr
-rwxr-xr-x    1 root     root      47287862 Jun 13 15:59 docker
-rwxr-xr-x    1 root     root        387564 Jun 13 15:59 docker-init
-rwxr-xr-x    1 root     root       2714295 Jun 13 15:59 docker-proxy
-rwxr-xr-x    1 root     root      68107552 Jun 13 15:59 dockerd
-rwxr-xr-x    1 root     root      12073312 Jun 13 15:59 runc

root@WDMyCloudEX4100 docker-20.10.7 # ls -al /sbin | grep docker
lrwxrwxrwx    1 root     root            47 Jul 15 21:29 containerd -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/containerd
lrwxrwxrwx    1 root     root            52 Jul 15 21:29 containerd-shim -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/containerd-shim
lrwxrwxrwx    1 root     root            60 Jul 15 21:29 containerd-shim-runc-v2 -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/containerd-shim-runc-v2
lrwxrwxrwx    1 root     root            40 Jul 15 21:29 ctr -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/ctr
lrwxrwxrwx    1 root     root            43 Jul 15 21:29 docker -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/docker
lrwxrwxrwx    1 root     root            48 Jul 15 21:29 docker-init -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/docker-init
lrwxrwxrwx    1 root     root            49 Jul 15 21:29 docker-proxy -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/docker-proxy
lrwxrwxrwx    1 root     root            44 Jul 15 21:29 dockerd -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/dockerd
lrwxrwxrwx    1 root     root            41 Jul 15 21:29 runc -> /mnt/HD/HD_a2/Nas_Prog/docker/docker/runc

If the contents of the directory in the first snippet does not match the file names above it will cause an issue and then if the symbolic links in the second snippet are not created in /sbin, this will also cause an issue. These should be created by the start scripts for docker though.

Cheers,

JediNite

[mrbscott]

Thank you @JediNite (very appropriate name if I do say so myself.) It would appear I ran into an IDT10 error when replacing the files yesterday and had missed containerd-shim-runc-v2. I also misunderstood how to setup the port forwarding to the container which fixed the connection issue.

[scuba-fan]

Still unable to get Docker running due to port 9000 use by Twonky. Followed #49 and #58 to know avail.

[JediNite]

Still unable to get Docker running due to port 9000 use by Twonky. Followed #49 and #58 to know avail.

@scuba-fan,

You have not given any more details on what the issue is you are seeing here exactly. Couple possible ways to resolve : 1.) Disable the use of Twonky Server and use something different for media streaming. 2.) Change portainer to use a different port. You can edit the "update_portainer.sh" script so that portainer runs on a different port (eg. change "9000:9000" to "9001:9000" within the script). This would then remap a different port on the NAS to the portainer container port 9000.

Cheers,

JediNite