trurl

You can go directly to the correct support thread for any of your dockers by clicking on the docker in the webUI and selecting Support.

The Unraid templates in most cases are created by the docker developers themselves. Those docker developers are the fellow Unraid enthusiasts of which you speak. You can find those docker developers in the support threads they have also created for their containers in our Docker Containers subforum. This MSSQL container was not one of these of course.

Earlier in this thread you were having a problem because your VMs were autostarting and I told you how to edit a file on flash to disable the VM Manager. If you did edit that file then that is the reason.

Why did you quote the instructions on getting us the required information, but didn't actually bother to follow those instructions? Here is the link he mentioned that is in his signature: https://forums.unraid.net/topic/57181-docker-faq/#comment-564345 That is also the very first link in the Docker FAQ. It might be worth your while to read other posts in that FAQ too.

That only applies to mixing user shares with disks that are part of user shares. The problem arises because linux doesn't realize that the source and destination may be the same file, since user shares are just another view of the disks. Unassigned Devices are not part of user shares, so that problem does not apply.

Looks like it is having problems with your cache SSD. Check connections.

Something like that. I'm not entirely sure how things go with startup though since I haven't tried it. You would want it mounted before the docker service starts.

Unassigned Devices are not part of user shares. We were talking about using it as a cache drive. You have to stop the array and assign it to a cache slot in Main - Cache Devices. You will have to format it after adding it. If you think you might add additional cache devices then you have to format as btrfs.

If you can't get into your server over the network then you will have to do it locally with keyboard and monitor. Even mouse if you boot GUI mode. You will need to get us Diagnostics.

More RAM would be better.

Don't cache initial data load, cache just gets in the way. But do install cache before setting up dockers and VMs so they will go on cache where they belong. It is a bit of trouble to move them to cache later.

In fact, using an SSD in the parity array is NOT recommended. SSDs in the array can't be trimmed, their performance would be limited by parity, and there is a question of whether some SSD implementations could invalidate parity. So put it in the cache pool.

I have 2x275 SSD as btrfs raid1 cache pool. I converted my array to XFS early in V6 and haven't tried anything else. @johnnie.black is the btrfs expert. As for "pinging" other users, you have to start typing and then actually make a selection from the matches. Typing the whole thing doesn't work. Like this: @Rustbucket

Since you have some new and empty disks, the best time to convert your filesystems is before doing anything else, since conversion means reformatting. So you will want to format the new disks (XFS or btrfs) then copy the data from your ReiserFS disks so you can reformat them. Most people format array disks as XFS but btrfs is also available and btrfs is required for cache pools.

So have you actually upgraded to Unraid 6 yet?

The simplest and best thing to do with docker image is to just delete it and recreate it. According to your diagnostics, your system share is cache-prefer, so it would be recreated on cache. Then Apps - Previous Apps will add your dockers just as they were.

I only work directly with the disks when using mc. You must never mix user shares and disks when working with the files since linux won't know that the source and destination may actually be the same file.

At the terminal, typing mc will launch Midnight Commander, a text-GUI file manager similar to the Commander type file managers from the DOS days. It is pretty easy to figure out, and a lot of information on the web about using it.

You can't move open files so you will have to go to Settings and disable the Docker and VM Manager first.

Often it turns out to be different in many ways instead of the exactly same, so better to keep the discussions separate.

Simplest is to just shutdown and put your flash drive in your PC.

Since you don't have any VMs yet, you can just disable VMs in VM Manager then delete those libvirt folders. You don't want them on the array and if you recreate them they should get recreated on cache anyway. Same for Docker, disable and then delete those docker folders. Then you can recreate docker image and it should get created on cache where it belongs. Apps - Previous Apps will add your dockers just as they were. Do you know how to work at the command line to delete those folders? I usually just use the builtin mc (Midnight Commander) when working with files and folders directly on the disks. Then the system share should only exist on cache.

On your flash drive, in config/shares, there should be a .cfg file named for each user share, such as appdata.cfg. If you want to get rid of those files that aren't used anymore, you can just delete them and only keep the .cfg files that correspond to the user shares you currently have as shown in that screenshot. It would make your diagnostics somewhat less trouble to wade through. I've never run my dockers from an Unassigned Device so I'm not entirely sure how that works. I assume you would want the UD to automount but I don't know if there is something else needed to make sure the docker service doesn't start until after that mount. Maybe someone else can chime in here.

Some people do it that way but you have to take a little more care when setting up your dockers. Do you have a good understanding of docker volume mapping? Your screenshot is about what I expected, but I just wanted to make sure because your flash drive has a lot of files in config/shares (where the user shares configurations are stored) that don't appear to be used and their (anonymized) names seem very peculiar. Possibly you accidentally created a lot of user shares at some point by copying a lot of things to the top level of a disk.

Are you maybe trying this from Safari again?