So...I've finally got Ambar docker up and running with a few bugs yet to work out...but during the celebration of completing the massive frustration of configuration options of all of the different dockers, I had a heart drop for a moment. The user shares all disappeared (but disk shares and drive space didn't change)...so remembering that user shares are dynamically created, and figuring something with unraid just crashed in the background, I attempted to clean reboot (after waiting for a long while for attempt to unmount user shares).  Everything came backup up ok afterwards, but I'm thinking that my docker mappings had something to do with the crash.

 

I was relating docker location(s) IE "/usr/share/elasticsearch/data" directly to "/mnt/user/appdata/ambar" via docker config paths. At some point as I was restarting several dockers at once a few times over, the crash occurred. (I pulled a diag beforehand just in case anyone wants to fish out the source issue).

 

Is there something wrong with directly relating the above folders that would cause the user shares to crash like that?  Is there a better way to refer docker data to a cache drive (that doesn't move certain folders to the array)?

seems fine to me, but i would use 

 

/usr/share/elasticsearch/data -> /mnt/user/appdata/ambar/data

 

Without any log and or error we can say anything about the crash, might not even be the docker. Might be as simple as run out of RAM.

Edited April 25, 20197 yr by nuhll