Having just upgraded from 5.0.5 to 6.0-beta12, I cannot get docker to save 'Template repositories:' location or to even start and the guides here are 20+ pages of Q&A posts on a post for beta3, which looks nothing like what I am seeing on Beta12.
Can we have a locked forum on how to start Docker for non-Linux users please?
Whilst I love the core functionality of unraid to store my files, I find myself having to hire other people to remote into my server every time there is a new build or new plugin, because I don't know Linux commands, nor have the time to, when there are turnkey solution for other NAS products or wizards provided for Windows based operating systems to do the same thing.
After upgrading to the latest build and following some guides here, all I have managed to do is to set the docker image location and the default image size and that's it.
The start button will not start the app.
The Template Repositories will not save any settings and there is no where to go for help other than whinging on the forum as there is no up to date guide on the forum.
Can anyone advise what this means in the logs or does anyone want to earn $$ to setup up some docker apps or plugins or xen or whatchmecallits as unraid is not built with the end user in mind for compatibility with third-party apps in my experience over the last three years.
And yes, after a few hours, I am already thinking of downgrading back to 5.0.5 as it works...
Frustrated user
/usr/bin/tail -n 42 -f /var/log/syslog 2>&1
Jan 25 16:53:01 Tower kernel: BTRFS: flagging fs with big metadata feature
Jan 25 16:53:01 Tower kernel: BTRFS: creating UUID tree
Jan 25 16:53:01 Tower php: Resize '/var/lib/docker' of 'max'
Jan 25 16:53:01 Tower php: starting docker ...
Jan 25 16:53:01 Tower kernel: BTRFS: new size for /dev/loop8 is 10737418240
Jan 25 16:53:11 Tower php:
Jan 25 16:53:27 Tower php: /etc/rc.d/rc.docker start
Jan 25 16:53:27 Tower php: starting docker ...
Jan 25 16:53:37 Tower php:
Jan 25 16:54:08 Tower php: /etc/rc.d/rc.docker start
Jan 25 16:54:08 Tower php: starting docker ...
Jan 25 16:54:18 Tower php:
Jan 25 16:55:38 Tower php: /etc/rc.d/rc.docker start
Jan 25 16:55:38 Tower php: starting docker ...
Jan 25 16:55:48 Tower php:
Jan 25 16:57:47 Tower php: /etc/rc.d/rc.docker start
Jan 25 16:57:47 Tower php: starting docker ...
Jan 25 16:57:57 Tower php:
Jan 25 16:59:20 Tower php: /etc/rc.d/rc.docker start
Jan 25 16:59:20 Tower php: starting docker ...
Jan 25 16:59:30 Tower php:
Jan 25 16:59:40 Tower php: /etc/rc.d/rc.docker start
Jan 25 16:59:40 Tower php: starting docker ...
Jan 25 16:59:51 Tower php:
Jan 25 17:00:30 Tower emhttp: read_line: client closed the connection
Jan 25 17:02:38 Tower php: /etc/rc.d/rc.docker start
Jan 25 17:02:38 Tower php: starting docker ...
Jan 25 17:02:48 Tower php:
Jan 25 17:53:59 Tower php: /etc/rc.d/rc.docker start
Jan 25 17:53:59 Tower php: starting docker ...
Jan 25 17:54:09 Tower php:
Jan 25 18:00:07 Tower kernel: mdcmd (57): check CORRECT
Jan 25 18:00:07 Tower kernel: md: recovery thread woken up ...
Jan 25 18:00:07 Tower kernel: md: recovery thread checking parity...
Jan 25 18:00:07 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks.
Jan 25 18:51:08 Tower php: /etc/rc.d/rc.docker start
Jan 25 18:51:08 Tower php: starting docker ...
Jan 25 18:51:18 Tower php:
Jan 25 18:53:37 Tower emhttp: shcmd (796): /usr/sbin/hdparm -y /dev/sdf &> /dev/null
Jan 25 18:59:15 Tower php: /etc/rc.d/rc.docker start
Jan 25 18:59:15 Tower php: starting docker ...
Jan 25 18:59:25 Tower php: