Hi

Sorry if a solution for this has been posted before but i am having some issues with docker

Ran in to a problem with docker where it complained about disk space eventhough i had 1,5 TB left. I read somewhere that i should try expanding the logs by running the following command: mount -o remount,size=384m /var/log

This however did not help so i tried rebooting the system and now docker seems to be gone. For some reason i cannot even bring it back by resetting it and disableling and enabeling it.

 

Hopefully someone can help me bring back Docker.

 

I have attached the diagnostics file.

diagnostics.zip

Syslog only covers a couple of minutes after boot. Says it can't create docker.img on your cache drive. Are you having any problem accessing other files on cache? Drives look OK so maybe filesystem corruption.

Sorry if my answers are crap but im very new to the world of Unraid or Linux in general..

 

If i try to browse the cache drive via the webgui i only get the parent directory which shows me nothing.

I can see that it has used 98 MB of space but i dont know on what

 

But in not sure if i have used the drive for anything else but cache. I have only been using Unraid with PLEX so far so i dont know if it should show anything

Do you have any User Shares configured to use cache?

I just made one (Or at least i think i did. I said "Yes" to use cache) but for some reason i cant enter the share. I dont have rights to do so. Dunno why. Every other share i have uses that login

Stop whatever you're doing...  Here's your entire problem:

May 26 11:09:55 Tower emhttp: shcmd (36): set -o pipefail ; mount -t ntfs -o noatime,nodiratime /dev/sdc1 /mnt/cache |& logger
May 26 11:09:55 Tower kernel: ntfs: driver 2.1.32 [Flags: R/O MODULE].
May 26 11:09:55 Tower kernel: ntfs: volume version 3.1.
May 26 11:09:55 Tower logger: mount: warning: /mnt/cache seems to be mounted read-only.

along with potentially this:

May 26 11:07:18 Tower logger: plugin: installing: /boot/config/plugins/apache.plg

because of this:

May 26 11:07:21 Tower emhttp: unRAID System Management Utility version 6.1.8

 

 

Problem 1 - NTFS formatted cache drive. (Obviously previously formatted in a windows box). unRaid for some reason allows NTFS cache drives, but it doesn't actually support them.  You're going to have to stop the array and format the cache drive as XFS (change the format from auto to XFS)

 

Problem 2 - There is no 6.1.x compatible apache plugin, and you really should uninstall it.

 

I'd suggest two things here, after fixing the format of the cache drive

 

#1 - Install Fix Common Problems Plugin and do whatever it suggests

#2 - Setup a docker.img file (20G should be sufficient), and then install Community Applications and select an apache docker app.

Hi

I've done the things you suggested but still i cant see the docker app in the GUI. Im not sure what im doing wrong here.

Hi

I've done the things you suggested but still i cant see the docker app in the GUI. Im not sure what im doing wrong here.

Then post a screen shot of the docker settings, and your diagnostics again

Of course. Here they are

Diagnostics_2.zip

I think that you should stop the docker service, delete the image file (a checkbox will be there and a delete button), and then recreate it.  Not quite sure what's happened, but the docker log shows this:

time="2016-05-29T08:11:27.409309243-07:00" level=fatal msg="Error starting daemon: Couldn't create Tag store: EOF" 

 

(oh and update fix common problems, as the last rev or two has better logging)

 

If that doesn't get you anywhere, reset the machine, run fix common problems again, and then post the diagnostics again (so that it'll be 100% clean without all of the fixes etc that you've already done)

 

As an aside, the logging from fix common problems is more useful than I figured it would be as people here can see exactly what was wrong, and then see the results as you've made the adjustments

If you start all over again, I recommend you create the image file on the top level of your cache drive, i.e. /mnt/cache/docker.img

 

(did you set the Docker folder as cache only?)

If you start all over again, I recommend you create the image file on the top level of your cache drive, i.e. /mnt/cache/docker.img

 

(did you set the Docker folder as cache only?)

bonienl, out of curiousity, do you have a clue why the docker image is being mounted as loop1 (and earlier in the syslog its showing a EXT-FS mounting of loop0?  I thought the docker image always got mounted as loop0  (or is the VM related?)

Thats just an ordering thing of when events happen. There are other image files mounted as loopback, I think the vm image containing the configuration is another.

... out of curiousity, do you have a clue why the docker image is being mounted as loop1 (and earlier in the syslog its showing a EXT-FS mounting of loop0?  I thought the docker image always got mounted as loop0  (or is the VM related?)

 

loop0 is assigned to docker, while loop1 is assigned to libvirt (VM)

df -h
/dev/loop0       20G  3.0G   16G  16% /var/lib/docker
/dev/loop1      1.0G   17M  857M   2% /etc/libvirt

 

... out of curiousity, do you have a clue why the docker image is being mounted as loop1 (and earlier in the syslog its showing a EXT-FS mounting of loop0?  I thought the docker image always got mounted as loop0  (or is the VM related?)

 

loop0 is assigned to docker, while loop1 is assigned to libvirt (VM)

df -h
/dev/loop0       20G  3.0G   16G  16% /var/lib/docker
/dev/loop1      1.0G   17M  857M   2% /etc/libvirt

May 29 08:11:05 Tower logger: starting docker ...
May 29 08:11:05 Tower kernel: BTRFS: new size for /dev/loop1 is 37580963840

May 27 05:48:06 Tower kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
May 27 05:48:06 Tower emhttp: Starting libvirt...
May 27 05:48:06 Tower logger: Starting libvirtd...

I suppose - as with most Linux settings - numbers are not fixed and depend on who comes first, as mentioned by Brit... (haven't really checked this particular instance)

 

Thank you all for your help so far.. Really appreciate it

 

I cant delete the folder from docker. The delete button isnt there. I dont think it has even made the folder.

 

I have rebooted the system

Performed a new Fix Common Problems test with nothing found

Diagnostics_Post_Reset.zip

When you stop docker and enter a new location for the docker image /mnt/cache/docker.img. Does it get created?

 

I think you didn't re-enable Docker when you stopped it or after the restart

 

Hmm.. No idea what changed.. I tried making the Docker again. This time directly in /mnt/cache/ instead of /mnt/cache/Docker/ and it worked.. Docker is back

 

What exactly changes between putting docker in cache or on the disks?

Hmm.. No idea what changed.. I tried making the Docker again. This time directly in /mnt/cache/ instead of /mnt/cache/Docker/ and it worked.. Docker is back

 

What exactly changes between putting docker in cache or on the disks?

If for no other reason, it should be on the cache drive for performance alone.  But problem solved is problem solved...

True.. Thanks, you guys for helping me fix the problem