Hi All,

 

I'm having a problem after upgrading to 6.2,

 

The locations i have been using are,

/mnt/disks/VMs/Docker/docker.img/
/mnt/disks/VMs/Docker/appdata/

 

I upgraded via the GUI straight from 6.1.9 and run my docker image and appdata directory on a btrfs ssd kept out of the array via Unassigned Devices.

 

After restarting and booting into 6.2 i went to the docker menu and deleted my old img as prompted, but unraid would not create a new img and docker remained 'not running'. After some playing around i discovered if i changed the location to the cache drive, a new img was created with no problem. I then tried to copy the image back to my preferred location on the ssd, but got the following message and docker would again not start,

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!

If i copied the img back to the cache drive however, docker starts with no issue.

 

Also, the appdata directory has been on the ssd the whole time and has worked as expected when i reinstalled my containers.

 

Its almost like there's a record somewhere preventing a new img being created in the location of the old one?

 

I'd be grateful if anyone can help me with a solution, as i'd like the img back on my ssd instead of my cache drive and would prefer not to have to start my wipe my flash drive and start from fresh.

 

Rich

 

Most users have problems with docker.img stored on an unassigned disk.  Known issue.  See the docker FAQ or post 2/3 of the 6.2 announcement

 

Sent from my LG-D852 using Tapatalk

 

 

Thanks for the quick reply.

 

That's annoying, especially as it was working perfectly before 6.2 

I've just tried a clean install of my flash drive and have exactly the same problem, so obviously it's not due to anything lingering after upgrading.

 

I did have a quick look through the FAQ but i'll check it out again and look at the 6.2 announcement too.

 

Thank you

You were right, it's fully explained in the announcement. For some reason google didn't pick that up when I was searching earlier.

 

Thanks for pointing me in the right direction 

 

Rich