ksculland Posted April 9, 2016 Share Posted April 9, 2016 I am very new to unRaid. Day 1 - Pieced together my 1st server. I have 4 drives setup and working Day 2 - Trying to learn about dockers but can't since I don't have a Dockers Tab. I did go to Settings, Docker icon and ensure Enable Docker: YES was selected. Can anyone please give me some suggestions for what to do next. Thanks, Kirk UnRaid Version: 6.2.0-beta21 CASE: Thermaltake Xaser III V1000D Blue Power Supply: Seasonic M12II EVO 620W CPU Type: AMD Phenom II X6 1090T Black Edition, 6x 3.20GHz Motherboard: Gigabyte GA-890GPA-UD3H Ram: 16GB - Corsair Vengeance Video Adapter: Onboard Disk Drive 1: WD Red 3TB (Parity 1) Disk Drive 2: WD Red 3TB (Parity 2) Disk Drive 3: WD Red 3TB (Data xfs) Disk Drive 4: WD Red 3TB (Data xfs) Link to comment
BRiT Posted April 9, 2016 Share Posted April 9, 2016 Toggle Docker Enabled setting to No, then back to Yes. Link to comment
ksculland Posted April 9, 2016 Author Share Posted April 9, 2016 No Dice, but thanks. Link to comment
BRiT Posted April 9, 2016 Share Posted April 9, 2016 Post the Diagnostics.zip file. Maybe the error is in there. Link to comment
ksculland Posted April 9, 2016 Author Share Posted April 9, 2016 Diagnostics.zip file attached. Path for the libvirt image: I tried default set paths and also created my own set as well, but no difference. diagnostics.zip Link to comment
saarg Posted April 9, 2016 Share Posted April 9, 2016 I was thinking VM's for some reason in my previous post. Did you specify a docker vdisk size before enabling dockers? Link to comment
ksculland Posted April 9, 2016 Author Share Posted April 9, 2016 Default was set to 10gb. I have also rebooted the system a few times. Link to comment
BRiT Posted April 9, 2016 Share Posted April 9, 2016 I think your docker path isnt fully specified. In your syslog are the following errors: /mnt/disk1/Docker is not a file. Try specifying your docker filename as /mnt/disk1/Docker/docker.img Link to comment
BRiT Posted April 9, 2016 Share Posted April 9, 2016 Oh, you have a space in your docker share. Try it as DockerFiles and not "Docker Files". Link to comment
ksculland Posted April 10, 2016 Author Share Posted April 10, 2016 SOLVED!!! Thanks I was not aware spaces in directory names were not permitted. Link to comment
Squid Posted April 10, 2016 Share Posted April 10, 2016 SOLVED!!! Thanks I was not aware spaces in directory names were not permitted. You're supposed to be allowed to (after all, if you weren't, why does the system's drop down allow you to select a share that contains a space?) Posted a note in the 6.2 thread here http://lime-technology.com/forum/index.php?topic=48193.msg463203#msg463203 Link to comment
METDeath Posted April 10, 2016 Share Posted April 10, 2016 As a noteworthy thing... you will get better docker performance if you have the docker.img on either your cache drive (SSD, right?) or a drive outside your array as changes to the image will not require the parity drive to spin up. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.