trurl

That means it knows about the file, but can't find it. So it must be seeing your appdata, which is where your plex library is, but you haven't mapped your Media the same as before, so it can't find the file where the library says it should be. That looks like it would work, if and only if, that is what you had before. With that mapping for your Media user share, Plex would see it at /Media. It must be exactly the same as you used before, including matching the same upper/lower case you used before. And the fact that it couldn't find anything when you rescanned also suggests you have the wrong container volume, since it is just going to look in the same place you set it up before. For example, if you used /media for the container volume before, then that is where the library thinks it should be, not /Media. Also, you should always have a current backup of your flash drive. Go to Main - Boot Device - Flash - Flash Backup to download a zipped copy of your flash any time you change any settings in the webUI.

What version Unraid and what version plugin?

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

Limited test release. Since nobody looks at sigs, and most don't have them even enabled since they are turned off by default, you are only the 2nd person to notice.

According to the mapping you posted, /transcode is mapped to /tmp. That is fine. The only confusion was your mentioning /TMP, which you have not mapped. If, in the settings within Plex, you tell it to transcode to /transcode, then since that is mapped to /tmp, that is where it will go on the Unraid host. The only problem would arise if you told Plex, within its settings, to transcode to something other than /transcode. If you tell it to transcode to something with isn't mapped, such as /tmp or /TMP, it will wind up in the docker image.

As mentioned, you shouldn't really be using "root" to access shares on the network anyway. "root" will work, but just the same as "some_random_user" would work, as a guest user that only has access to public shares. What do you get from the Windows Command Prompt with this? net use

Not exactly sure where things are not working from your description. You really shouldn't use the root user for accessing shares over the network anyway, though it should work (as a guest) assuming you are only trying to access a share with Public access. Go to Credential Manager and delete the credential for your server so Windows can renegotiate it.

Perhaps the other side of this puzzle is the fact that Windows will only let you log in as one user to another computer on the network, and if you have already established a connection as one user, it won't let you use another user even though it will prompt you to log in. You have to get rid of the login it has already established before Windows will let you use a different one. Control Panel - Credential Manager.

What exactly do you mean by the username for your server? The webUI and command line of your server can only be accessed by the "root" user. Shares are accessed by users you create in Unraid, depending on the security settings for each share. "root" only has guest access to shares over the network, the same as any user that does not have a login. Have you created any users in Unraid for accessing shares over the network?

Also, your system share is cache-only but has files on disk1.

It means you have filesystem corruption on that disk, which in this case is your cache disk. https://wiki.unraid.net/index.php/Check_Disk_Filesystems

And it seems likely a moot point for this particular user since he wasn't even aware of the application.

I have my automated flash backup going to an NTFS formatted USB Unassigned Device which I can just plug in to Windows. Another possibility is using an SMB Unassigned Device on another computer. Note though that if you specify a path to an Unassigned Device, and it isn't mounted, that path will be in RAM.

The most important thing if you can't get that config backup is knowing your disk assignments. We can get those from the diagnostics you posted earlier. That will allow you to reassign your disks and all your data will be there. Unfortunately, you will have lost all the other configuration you did in the webUI. Some of that can be recovered from those diagnostics, but some of the more difficult things, such as docker settings, can't be. https://forums.unraid.net/topic/61211-plugin-ca-appdata-backup-restore-v2/

Put flash in PC and let it checkdisk. While there make a copy of the config folder. The config folder is all you will need to get going again with a new install. I don't know if that flash can be reused or not. @Squid seemed to think no. In any case, if you copy that config folder backup to a new install on that flash or another, you will be good to go with everything as it was. If a new flash, you will have to go to Tools - Registration to get a new key for the new flash. For future reference, you should always keep a current backup of flash. You can easily get a zipped copy of flash at Main - Boot Device - Flash - Flash Backup.

/tmp and /TMP are not the same, Linux is case-sensitive. It is true the if you specify /TMP you will create a root folder named TMP, but it is not the /tmp folder the OS already has created in RAM, and it is not the same as /tmp that is specified in that screenshot for the /transcode mapping. I don't know which of these you told Plex to use. Assuming you have Plex setup to transcode to /trancode, then it will use /tmp, since that is what is in the mapping. If you told Plex to use /TMP (or even /tmp) that is not mapped and so would be in the docker image.

Where exactly did you get a template? If you are referring to the template created by the Add Container page mentioned by Squid, you can only expect that to work if you actually filled out all the necessary details for that docker to work in the Add Container page yourself. I found the github for that particular docker here: https://github.com/aaronweaver/docker-DefectDojo The documentation talks about installing it with docker-compose from the command line. The builtin method for installing a docker using the Add Container page doesn't work that way. That may not be exactly the right one after all, though it does seem to be the same github user. And in general, any random docker on docker hub (if it even works) is going to probably require you to understand how to use docker and figure out whatever documentation (if any) is given by that docker author. The Apps page tries to help a little but you are mostly on your own for those. Even if it is something that can be installed from the webUI, you will have to figure out how to fill out most of the Add Container page details yourself. Since the Apps page is really a plugin, and not part of any Unraid release, and since there is no evidence this is a problem with this release, I am going to change its priority to "Other" and Close it. This should have been posted in one of the regular subforums. If you think you have something that belongs in a Bug Report, be sure to follow the report guidelines: https://forums.unraid.net/bug-reports/stable-releases/report-guidelines-r68/

Post your docker run command as explained here: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

Looks like you rebooted between this post and your last. What I was looking for in your diagnostics would have gone away with the reboot until it happened again. Specifically, I was looking to see if something had filled up rootfs. I don't know if there was anything to the idea or not.

These suggests you may have other problems. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

If a docker application has a webUI you can access it by simply clicking on that docker's icon in the Unraid webUI and selecting WebUI.

Dockers are just applications written by someone else and made into containers by the Unraid developers. Many applications have their own website and forum. If you are having a problem getting the container installed then the support thread for the container is going to be the best place to ask. If you have a problem or question about the application itself you might be better off checking out the website for the application. There is a link to the website for the application in the first post in this thread. That is typical for all docker support threads.

In response to your report of your own post. Your post was hidden because you had not yet been approved for posting on the forum. We get a lot of spammers so we have to approve the first post of any user. Did you see the response to mcjfauser? Do you understand volume mapping? Some of those seem like a shot in the dark. Since I don't use any of those containers, I will just direct you to the Docker FAQ and let others help you with the details. https://forums.unraid.net/topic/57181-real-docker-faq/ This in particular might be relevant: https://forums.unraid.net/topic/57181-real-docker-faq/?page=2#comment-566086

The container authors just make dockers containers of applications written by someone else. This one uses the arch linux version of ruTorrent.