So I installed the fix common problems plugin and it says I'm using "user" as a share name. Well, I checked, i don't officially have any share named "user". What I do have is:

 

/mnt/cache/user where all the docker / VM stuff is (appdata, isos etc.)

 

/mnt/user which contains all my shares + another "user" folder which is the exact same one as the one in /mnt/cache (same files etc.) ?

 

/mnt/user0 which again contains all my shares (???)

 

Everything seems to work fine, but I think it shouldn't look like that and probably will break my array and/or cache raid when updating or else... how do I fix this without killing my array or cache raid?

All top level folders on array drives or pools are treated as User Shares so the error message is correct.    You need to stop using /mnt/cache/user to avoid this.

55 minutes ago, drdoolittle79 said:

/mnt/cache/user where all the docker / VM stuff is (appdata, isos etc.)

Putting these in a non-standard place like this is just going to make things more complicated for you even if you had named that folder /mnt/cache/stuff.

 

 

Thanks! Thing is guys: I can't remember that I created that user folder? Maybe when I set up docker.

 

Nevertheless, as my installation was quite new I deleted the whole user/user folder and reinstalled my docker images / VMs.

Precursor, I am somewhat of a linux noob.I am having the exact same issue when using the Fix Common Problems plugin. I have 2 NVMe drives, one I use for cache, and one I want to dedicate to Docker installs, along with my 4 disk array.

Browsing File Manager, I see appdata in two locations.

/mnt/docker/user/appdata (location is on docker)

/mnt/user/user/appdata (location is on docker)

I also see a /mnt/user0. I created a user for shares, and I assumed that this was created when doing so. Is that incorrect?

Like DrMutaba, everything seems to be working ok. I currently only have 2 Docker installations (Plex and Homebridge), but want to insure that I know what I am doing. I don't want to delete anything important and screw something up in the process. Can anyone advise?

user0 is just the user shares excluding files in pools (not the array). You probably shouldn't use that.

But those paths mean you have a user share actually named 'user'. I don't recommend doing that and no good reason to.

Attach Diagnostics ZIP to your NEXT post in this thread.

Wow, thank you for quick response :)

hmm, I dont recall creating a user share named user either. Maybe I put something incorrect when adding a docker install location. Not sure. Attaching diagnostics.

manteo-diagnostics-20250626-0727.zip

1 hour ago, lumbeecheraw75 said:

Maybe I put something incorrect when adding a docker install location

Any folder at the top level of array disks or pools or /mnt/user is automatically a user share named for that folder. Those paths you specified created a folder named 'user' at the top level of your 'docker' pool and/or /mnt/user.

In fact, when you setup docker, you specified

DOCKER_APP_CONFIG_PATH="/mnt/docker/user/appdata/"

So that means the default path for your appdata is going to create that user share named 'user'.

Get rid of the 'user' portion of that path. And you will need to move all of your appdata up a level, into /mnt/docker/appdata.

Post a screenshot of your User Shares page.

I was looking at just that a few minutes ago and wondered if that was the culprit, but your explanation clarifies a bit.

here is the user shares page. I moved some stuff around since I sent over the diagnostics.

so the adjustment needs to be at the docker settings level and not per container?

made changes to docker settings, and an appdata share was created. not certain this is correct but Fix common problems now shows no errors.

Your diagnostics and screenshots don't show a user share named 'user'. Perhaps you got rid of it?

You need to specify /mnt/docker/appdata, not simply /mnt/docker, for the appdata path. Putting your appdata directly into the top level of your 'docker' pool will result in folders at the top level of that pool, and so will create separate user shares for each container.

Also, changing that path in the docker settings won't affect any containers you already have installed so you will need to fix each of them separately.

I never got rid of any user shares. I'm currently making some adjustments based on your suggestions. I have updated the appdata path

I think I have things squared away. The plugin is not showing any errors. I moved the docker.img file to the NVMe drive. The appdata share remains (I assume this is expected). Thanks for your assistance. It is highly appreciated.

manteo-diagnostics-20250626-1000.zip

The "standard" share for docker.img is system, but it will be OK the way you have it now.

system user share doesn't exist since it has no files, but it looks like it is configured to have files moved to the array. Your VM Manager is currently disabled, but it also uses system share by default. And you don't want Docker or VM related files on the array so pay attention to these details if you ever enable VMs.

thank you, I will keep that in mind when I setup the VM Manager. I assume that system was on disk1 of the array before I moved it to the NVMe.

According to your diagnostics, system share doesn't exist. If you enable VM Manager with its current settings, it will be created since that is the path specified. But don't allow system or domains to be moved to the array.

21 hours ago, trurl said:

According to your diagnostics, system share doesn't exist. If you enable VM Manager with its current settings, it will be created since that is the path specified. But don't allow system or domains to be moved to the array.

yes I made changes to move it back from the docker_img share since you mentioned it on the 26th. I have it stored on the NVMe that I have docker apps writing to instead of the cache drive (which Im still not certain is best case usage for me. Considered just making a multi-device pool from the 2 NVMes). Im going to try VMs soon.

Edited June 28, 20251 yr by lumbeecheraw75