I just moved from a single xfs cache drive to a cache pool by copying the contents to a user share and back again (including the docker image) and now I'm getting the following warning:

 

Your existing Docker image file needs to be recreated due to an issue from an earlier beta of unRAID 6. Failure to do so may result in your docker image suffering corruption at a later time. Please do this NOW!

 

I'm on 6.1.9 and was never on a beta of v6. I'm sure I could recreate my docker image to get rid of this message, but is there a simpler way? I don't believe it really applies in this case.

I'm also suffering from this same error.

replaced a 128 gig ssd cache drive running xfs with a 256 gig running btrfs using the instructions from the wiki.

http://lime-technology.com/wiki/index.php/Un-Official_UnRAID_Manual#Replace_the_cache_disk

could anyone help?

i'd rather not have to reinstall and reconfigure 10+ dockers if i don't have to.

I'm also suffering from this same error.

replaced a 128 gig ssd cache drive running xfs with a 256 gig running btrfs using the instructions from the wiki.

http://lime-technology.com/wiki/index.php/Un-Official_UnRAID_Manual#Replace_the_cache_disk

could anyone help?

i'd rather not have to reinstall and reconfigure 10+ dockers if i don't have to.

Can't help with the actual problem, but will state that its a breeze to reinstall.

 

- Nuke the docker.img file

- Recreate it

- Reinstall the apps either through CA's previously installed or via Add Container (my* templates)

 

No re-configuring necessary.  Everything will be back up and running the exact same way it was before the nuke.

 

I think that has to do with the attributes on the file, i think it needs the NCOW flags set. (No Copy On Writes). Try setting that flag and see if that's all the management screen is looking for.

 

Search the forums for how to set it.

Thanks for the reply. So are you saying that copying the docker image from an xfs drive could induce the same bug as moving from a previous version of UNRAID?

 

Is there any benefit to recreating the image vs setting that bit?

Thanks for your replies.  I tried setting the bit to no avail.  I even tried the 'move the image to another folder with the bit set' trick - also no dice.

 

I ended up creating a new docker image, and re-downloaded the 11 docker apps.  Probably for the best,  as i had several stale docker apps in the past that were originally filling up the docker file.    At the time i created mount points outside the docker image for logs & temp files, but im sure the docker image itself was filled with garbage.