First time setting up a docker today and saw that my appdata folder looks like it is setup as a user share and will save across all the drives in the array. Would it be a better idea to save that folder just on the cache drive when setting things up?

Currently it is:

 

/mnt/user/appdata/crashplan  (or configs from other dockers)

 

Would it be better to just statically configure that path to something like:

 

/mnt/cache/appdata

 

Right now my cache drive is ONLY for the docker image, and that's all that is on it right now.

You MUST go to the Shares page and create the share with Use cache disk: Only

 

If you don't then mover will move it to the array.

You MUST go to the Shares page and create the share with Use cache disk: Only

 

If you don't then mover will move it to the array.

 

Yes, I have to go in reverse a little bit to do this. Now I know what I know, in hindsight I now see that I should have created the appdata/config folder first as a usershare to ONLY use the cache drive and not let the docker just create it by itself.

You MUST go to the Shares page and create the share with Use cache disk: Only

 

If you don't then mover will move it to the array.

 

trurl, I think you should add this line to your signature! 

You MUST go to the Shares page and create the share with Use cache disk: Only

 

If you don't then mover will move it to the array.

trurl, I think you should add this line to your signature! 

I do get a little tired of saying it. I started a whole thread about this to see if we could do something different to keep users from shooting themselves in the foot with this. The default behavior of unRAID almost encourages users to make this mistake.

 

Application Data: Cache-only Share or Hidden Folder?

 

You MUST go to the Shares page and create the share with Use cache disk: Only

 

If you don't then mover will move it to the array.

trurl, I think you should add this line to your signature! 

I do get a little tired of saying it. I started a whole thread about this to see if we could do something different to keep users from shooting themselves in the foot with this. The default behavior of unRAID almost encourages users to make this mistake.

 

Application Data: Cache-only Share or Hidden Folder?

 

I did read the other thread as well. I don't use mover and have ALL my shares that I setup manually NOT use any cache drive at all. Everything is written to the array and not the cache drive at all. Having folders appear that I have not created like "user0" just confuses me a little. I did create my docker image on /mnt/cache and ended up seeing the docker.img file in /mnt/user also by itself. I turned off dockers, since I wanted to remove Crashplan temporarily anyway and the docker.img file doesn't get deleted. Which is fine, I can just remove it manually. Do other users also see their docker image file in /mnt/user ? Load up the gun, I'll shoot myself in both feet tonight.

 

I have my docker.img at the top level of my cache drive, at /mnt/cache/docker.img. Mover will not touch files at the top level, only folders that are not cache-only.

 

/mnt/user is the "fusion" of all the array disks and the cache disk. /mnt/user0 is the "fusion" of only the array disks. The mover script uses rsync to move /mnt/cache folders to /mnt/user0 folders.

 

So, /mnt/cache/docker.img is also /mnt/user/docker.img, but it is not at /mnt/user0/docker.img

Don't worry about it opentoe, 'tis a common mistake, and I would never admit it in public, but I was setting up a new config and forgot to mark my appdata as cache only, one week later, mover ran overnight and it took me three hours to work out why half of my config files were missing.  But I'd never admit that on a public forum! 

I've added a second warning note about this to the Upgrade guide, Docker section.  I'm hoping that Jonp will consider adding warnings about it to the Docker guide.

I have my docker.img at the top level of my cache drive, at /mnt/cache/docker.img. Mover will not touch files at the top level, only folders that are not cache-only.

 

/mnt/user is the "fusion" of all the array disks and the cache disk. /mnt/user0 is the "fusion" of only the array disks. The mover script uses rsync to move /mnt/cache folders to /mnt/user0 folders.

 

So, /mnt/cache/docker.img is also /mnt/user/docker.img, but it is not at /mnt/user0/docker.img

 

Ok, by far these couple sentences make the most sense to me about what's going on. First time ever turning on a cache drive, so the ramifications of doing that made changes I've never seen, hence all the questions. Since I don't use the cache drive as a "cache" drive, is there a way to turn off mover and remove the /mnt/user0 folder? Or that's just inherent by design and live with it?

I have my docker.img at the top level of my cache drive, at /mnt/cache/docker.img. Mover will not touch files at the top level, only folders that are not cache-only.

 

/mnt/user is the "fusion" of all the array disks and the cache disk. /mnt/user0 is the "fusion" of only the array disks. The mover script uses rsync to move /mnt/cache folders to /mnt/user0 folders.

 

So, /mnt/cache/docker.img is also /mnt/user/docker.img, but it is not at /mnt/user0/docker.img

 

Ok, by far these couple sentences make the most sense to me about what's going on. First time ever turning on a cache drive, so the ramifications of doing that made changes I've never seen, hence all the questions. Since I don't use the cache drive as a "cache" drive, is there a way to turn off mover and remove the /mnt/user0 folder? Or that's just inherent by design and live with it?

 

Why don't you mount your drive with this and not use it as a cache drive at all?  I keep my docker.img on a drive that is not part of my array using this plugin here by gfjardim.  I do keep my appdata on my cache drive but you could easily change the config to keep it all outside of the array.

I have my docker.img at the top level of my cache drive, at /mnt/cache/docker.img. Mover will not touch files at the top level, only folders that are not cache-only.

 

/mnt/user is the "fusion" of all the array disks and the cache disk. /mnt/user0 is the "fusion" of only the array disks. The mover script uses rsync to move /mnt/cache folders to /mnt/user0 folders.

 

So, /mnt/cache/docker.img is also /mnt/user/docker.img, but it is not at /mnt/user0/docker.img

 

Ok, by far these couple sentences make the most sense to me about what's going on. First time ever turning on a cache drive, so the ramifications of doing that made changes I've never seen, hence all the questions. Since I don't use the cache drive as a "cache" drive, is there a way to turn off mover and remove the /mnt/user0 folder? Or that's just inherent by design and live with it?

 

Why don't you mount your drive with this and not use it as a cache drive at all?  I keep my docker.img on a drive that is not part of my array using this plugin here by gfjardim.  I do keep my appdata on my cache drive but you could easily change the config to keep it all outside of the array.

 

Thanks, I'll look into that. I guess since the docker.img file isn't backed up or the drive it is on fails...then you would need to start over with dockers, right? I assume that is why you keep your appdata on the cache drive, so it is part of the array?

 

The cache is not protected so neither is appdata.  The docker.img isn't really that important as it's so easy to create a new one and download the containers again.

 

The important things are the appdata folder and the XML files in the boot/config/docker directory (my-syncthing, my-tvheadend etc etc)

 

I use a script from the forum somewhere to backup my appdata to my array once a week.

 

I'm not really sure why I don't keep my appdata on the non-array disk come to think about it.  I think it may have been because I setup the docker.img on my non-array SSD for speed and I had several VMs on there as well so space was at a premium.  At the moment I don't have any VMs so I could migrate appdata to the SSD.