thanks for the tip
I have installed docker and docker compose on the Ultra Ex2 without much of a problem. The only thing is that I cannot set port 2375 to connect to portainer.io. If I set the port (within the daemon.sh shell) using -H …. docker will start but the container for portainer.io won’t. I get the message
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Does anyone have any idea how to correctly set this up?
Thanks
Wim
The firmware still ships with 1.7.
Is there anything special to do to upgrade from one version of your docker package (running 18.06.0-ce) to a new release? Just download the .bin and install it? Or do I need to stop what’s running first and do the upgrade?
Thanks
When upgrading a package, it goes through the following steps automatically:
Stop - Clean (disable) - Remove old package and then Install - Init the new package.
For this docker image, it does not remove the _docker directory, so all your containers and volumes are safe and the new binaries will pick them up just like that.
If you face issues, you may remove all docker data after disabling docker in the web UI and then
rm -rf /shares/Volume_1/Nas_Prog/_docker
Thanks, I jumped in and just did the upgrade by manually uploading the .bin file through the dashboard and all went well.
Hello,
I successfully installed Docker via web GUI, but can’t access to Portanner with 9000 port.
When I click ‘configure,’ it redirects me to http://192.168.1.103:9000 but says ‘This page can’t be displayed’
Also Docker compose is installed:
root@MyCloudPR4100 root # docker-compose --version
docker-compose version 1.24.0, build 0aa59064
root@MyCloudPR4100 root # which docker-compose
/usr/local/bin/docker-compose.
What shall I do right now?
Thank you.
OK, i am back again attempting to get it up and running on the DL4100.
I have installed the latest docker, which seems to work fine with a few exceptions.
# docker info
Containers: 3
Running: 1
Paused: 0
Stopped: 2
Images: 3
Server Version: 18.09.1
Storage Driver: vfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 96ec2177ae841256168fcf76954f7177af9446eb
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.38
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 5.819GiB
Name: WDMyCloudDL4100
ID: VVTX:QQ3A:SYBU:SWBB:2VRA:FB4A:QZWA:XRCV:22SY:TPGQ:UUH7:U6FZ
Docker Root Dir: /mnt/HD/HD_a2/Nas_Prog/_docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 26
Goroutines: 48
System Time: 2019-05-24T10:31:49.028676311-04:00
EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
# docker --version
Docker version 18.09.1, build 4c52b90
# which docker
/sbin/docker
# ls -l /var/lib
lrwxrwxrwx 1 root root 33 May 24 08:00 docker -> /shares/Volume_1/Nas_Prog/_docker
drwxr-xr-x 2 root root 0 May 24 07:39 dpkg
drwxr-xr-x 2 root root 0 May 24 07:39 samba
# ls -l ../_docker
drwx------ 2 root root 4096 May 24 08:00 builder
drwx------ 4 root root 4096 May 24 08:00 buildkit
drwx------ 3 root root 4096 May 24 08:00 containerd
drwx------ 4 root root 4096 May 24 09:01 containers
-rw-r--r-- 1 root root 202392 May 24 09:01 docker.log
drwx------ 3 root root 4096 May 24 08:00 image
drwxr-x--- 3 root root 4096 May 24 08:00 network
drwx------ 4 root root 4096 May 24 08:00 plugins
drwx------ 2 root root 4096 May 24 08:10 runtimes
drwx------ 2 root root 4096 May 24 08:00 swarm
drwx------ 2 root root 4096 May 24 08:12 tmp
drwx------ 2 root root 4096 May 24 08:00 trust
drwx------ 3 root root 4096 May 24 08:10 vfs
drwx------ 2 root root 4096 May 24 08:00 volumes
# sh stop.sh .
DOCKER stop: stop daemon
Remaining mounts:
# sh start.sh .
DOCKER START: setup daemon
DOCKER START: start daemon
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
22facdd234f6 nicolargo/glances:latest "/bin/sh -c 'python …" 26 seconds ago Up 14 seconds 0.0.0.0:61208-61209->61208-61209/tcp glances
I am unable to mount the docker.sock in a container.
When starting portainer, or glances this is the result:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/var/run/docker.sock\\\" to rootfs \\\"/mnt/HD/HD_a2/Nas_Prog/_docker/vfs/dir/629fa619f5aa122f98f5bb0e46084d1aa226cff9ae5c8c4aa988773af4a89004\\\" at \\\"/mnt/HD/HD_a2/Nas_Prog/_docker/vfs/dir/629fa619f5aa122f98f5bb0e46084d1aa226cff9ae5c8c4aa988773af4a89004/run/docker.sock\\\" caused \\\"invalid argument\\\"\"": unknown.
it is worth noting, in my logs there is this in regards to docker.sock:
time="2019-05-21T15:04:02.721782955-04:00" level=warning msg="could not change group /var/run/docker.sock to docker: group docker not found"
EDIT:
To further discuss the issue, it appears to be a permission issue. I also cannot mount /etc/timezone.
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/etc/timezone\\\" to rootfs \\\"/mnt/HD/HD_a2/Nas_Prog/_docker/vfs/dir/af35f714931fdf855de6b1fcc33b984490ab2f0cddf67f32f22df089eeb17ecb\\\" at \\\"/mnt/HD/HD_a2/Nas_Prog/_docker/vfs/dir/af35f714931fdf855de6b1fcc33b984490ab2f0cddf67f32f22df089eeb17ecb/etc/timezone\\\" caused \\\"invalid argument\\\"\"": unknown.
@bigrob8181 Have your tried deleting the Nas_Prog/_docker dir?
Make sure you stop/shutdown the daemon first (e.g. disable docker in the GUI).
After deleting it, reinstall the docker binary.
You’re working with docker v18.09 right?
So I’ve downloaded Docker install from https://wdcommunity.com/, but when I load it up on host:9000. I get Twonky Server and not Docker or Portainer. What is going on?
I followed your directions, shutdown docker via gui. Deleted _docker. Followed the commands above to reinstall. Rebooted. Same issues.
One thing i have noticed, there is not storagemapper folder in the newly created _docker folder. It is the only thing i can see that is missing from the _docker.bak folder.
I am working with 18.09 as indicated above in my previous post. Docker works fine minus mounting certain files/folders as volumes. Additionally the shutdown is not clean, i have to manually umount /mnt/HD/HD_a2/Nas_Prog/_docker.
I did just copy the storagemapper dir from _docker.bak to _docker to see if there is any other changes.
# cat /proc/self/mounts | grep docker
/dev/sda2 /mnt/HD/HD_a2/Nas_Prog/_docker ext4 rw,noatime,nodiratime,nobarrier,quota,usrquota,grpquota,stripe=128,data=ordered 0 0
# umount /mnt/HD/HD_a2/Nas_Prog/_docker
Good work with the docker update! For arm based drives I created docker-compose GitHub - aleksanderlech/armv7-docker-compose: Docker compose based on arm32v7/alpine
1 Like
Can i install docker on a WD My Cloud GEN2 ???
I wonder if anyone here could help me. Trying to get this running on an EX4100. I’ve downloaded and installed the binaries from wdcommunity. Disabled twonky etc.
This is what I’m seeing:
root@WDNAS docker # ./install.sh .
Installing with APPDIR: /docker / /docker
BusyBox v1.31.0 () multi-call binary.
Usage: cp [OPTIONS] SOURCE… DEST
Copy SOURCE(s) to DEST
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
-T Treat DEST as a normal file
-u Copy only newer files
./install.sh: cd: line 23: can’t cd to /docker
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0curl: (23) Failed writing body (0 != 1362)
No orig daemon found
ln: /sbin/*: File exists
Creating new docker root
./install.sh: line 68: /docker/daemon.sh: not found
./install.sh: line 73: /docker/daemon.sh: not found
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
I’ve tried a great many things, but I’m not an expert at this. Suggestions?
If you face issues, please create a new ticket on github.
No need to trigger everybody in this thread.
Did you find the fix? I have same issue with any container which needs volume mounted.
I have not. I am not convinced it works on the dl4100 despite the files being built. I abandoned the idea of having docker several times now, but keep coming back to try again. Actually today i am wiping the nas and attempting to start from scratch to see if there are any different results.
