read through a lot of guides and material to try and fix this, I'm not sure what the problem. please help 

tower-diagnostics-20211202-2221.zip

docker.img is read-only (corrupt), you will have to delete and recreate it.

 

Your appdata, domains, system shares are all on cache, as they should be, but you currently have them set to not use cache. Maybe you did this trying to fix your problem. Set those shares to cache-prefer or cache-only.

 

Your docker.img is configured to be at the root of cache instead of a user share. That is not technically wrong, but the usual place for docker.img is in system share on cache.

 

Delete and recreate docker.img

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

then reinstall your dockers

https://wiki.unraid.net/Manual/Troubleshooting#Restoring_your_Docker_Applications

Just now, trurl said:

docker.img is read-only (corrupt)

Have you had problems filling it?

@trurl

thank you for your quick response. 

my current docker settings after deleting the .img file 

 

i still get the same error: 

 

 

please advise. 

to answer your question : have you had problems filling it ? 

this is a fresh install, i never installed a single docker container so far, I've only been using the NAS features untill now. 

But i want to deploy containers in the future. 

 

post new diagnostics

here are the new diagnostics: 

 

tower-diagnostics-20211203-1502.zip

Sorry, I get it now. It is your cache that is read-only

 

 

Unrelated, but where is this coming from?

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.178.1.215  netmask 255.255.255.0  broadcast 192.178.1.255

 

192.178... is not a private IP

 

https://en.wikipedia.org/wiki/Private_network

 

Looks like that IP actually belongs to Google.

192.178.1. is my lan subnet | I setup this subnet on my Pfsense box. 

Just now, iamblackbird said:

192.178.1. is my lan subnet

Why didn't you use a private IP?

well it is private | i just didn't use the regular 10.10.. range and as this is behind my att gateway which has the 192.168... range 

from the link you sent above | can you give me more details on how to fix it please ? 

2 minutes ago, iamblackbird said:

well it is private

As mentioned, it belongs to google.

 

2 minutes ago, iamblackbird said:

how to fix it

Choose an IP from the allowed private IP ranges.

14 minutes ago, trurl said:

Sorry, I get it now. It is your cache that is read-only

 

not sure what I'm looking for in here. 

2 minutes ago, trurl said:

As mentioned, it belongs to google.

 

Choose an IP from the allowed private IP ranges.

I understand this is owned by google, but this is an internal subnet, I don't have this exposed to the internet, the public of the unraid box will be different. 

 

14 minutes ago, iamblackbird said:

link you sent above

You mean the link on fixing cache?

 

Can you actually write anything at all to cache?

 

1 minute ago, trurl said:

You mean the link on fixing cache?

 

Can you actually write anything at all to cache?

 

yes i am able to write to cache and i have some of my data on their. 

also i tried moving the location for the docker.img file to /mnt/disk2/system/docker.img and it seems to be working. although I'm sure if it is okay to do it this way. 

 

Please advise. 

 

okay, my bad - i am not able to write to cache, i had the cache preference set to NO for my drives. 

 

okay, so my problem now is to make my cache writable. 

 

Sorry for the delay.

 

Since you haven't yet installed any dockers (or VMs?), maybe the simplest thing would be to just reformat cache.

 

Is there anything on cache you want to keep?

On 12/4/2021 at 7:19 AM, trurl said:

Sorry for the delay.

 

Since you haven't yet installed any dockers (or VMs?), maybe the simplest thing would be to just reformat cache.

 

Is there anything on cache you want to keep?

 

so I didn't realize the cache was corrupted until I stopped the array and restarted it, once i restarted it - i saw the option to format un-mountable drives for the cache pool and proceeded to format it. now i don't seem to be having issues and docker seems to be working normally.

 

thank you for helping.