wgstarks

Did the docker create this folder when you configured the setting?

What happens when you drop a torrent file into whatever folder that container path is mapped to?

I usually figure on 150% of the largest file.

Google search suggests a restart.

I suspect that it may be related to the share settings then. Can you post a screenshot?

Your getting errors for no space left on device /media/Movies. Is there space? You should post your docker run command.

If you’re routing Radarr through a vpn container (ie qbittorrentvpn) then selecting webUI won’t work. Easiest thing to do (for me at least) is to just bookmark any containers this applies to. Actually, I bookmark all of my containers.

Are you attempting access using the IP of the Radarr docker?

I would suggest posting in the support thread for whatever plex docker you are running. In the docker tab click the plex docker icon and select support.

Yeah. Thanks. Been looking for an easy way to pull template updates but looks like I can either modify files that wont survive a reboot (I hate mc) or take screenshots of the settings, install a fresh version of the docker and configure everything all over again.

Here’s my run command for qbitvpn- You can see that I am using VPN_INPUT_PORTS and VPN_OUTPUT_PORTS but I don’t have anything set for the path “shared”. Not sure if I need to create that path or not. My template is pretty outdated. I see on GitHub that there is a default of “binhex-shared” so maybe I don’t actually need to add it to my template???

I try to avoid playing guinea pig.😁

I’ll just need to have screenshots of my configuration right?

It does for me.

External volumes would be anything outside of Appdata typically such as the paths you have defined in the container configuration. The default is to NOT back these up but you can change that by clicking the docker name. You should be cautious with this setting though. For example, if you have 20TB of movies and set Radarr to backup external volumes it's going to create backups for every movie.

I know I can manually add new paths, variables, etc in existing docker containers but determining the proper associated values isn’t really a simple process if you have many containers. Is there a process of deleting containers and re-installing that will pull new templates without losing existing settings?

@binhex Questions regarding “shared” path. 1) Can you give me an example of uses for this path? I doubt I have a need for it but want to be sure. 2) Can I create a dummy path to an empty share without causing any issues? Appdata Backup generates an error that this path does not exist every time a backup runs so I’m thinking if I create a dummy path that may solve the problem.

I think the main reason for the exclusion is that it can cause the backup to take a very long time when there are large numbers of small files (possibly hours) in the case of metadata. This means your docker will be shutdown for an extended period while waiting for the backup to complete. Also, if other dockers make changes to metadata, media, cache, etc during the backup process the backup will fail to verify. For me the artwork isn’t critical. Plex will grab it again if it’s lost. So I don’t worry about metadata. You can test for yourself if you like. See how long backups take without any exclusions and if any fail.

There is one item in the log- I’m afraid I don’t have any experience with ProtonVPN so not sure if this is part of your issue. It does appear just before the shutdown.

Looks like a few failed starts followed by a successful one. A few things, looks like a space between your LAN_NETWORK settings. Should be just comma separated. No space. If you are trying to access the webUI from 192.168.3.0/24 that should work though. Also, this container is designed to be used in bridge mode. Not sure if that’s part of your experience problem or not.

Attach your supervisord.log as well as your docker run command to your next post. Be sure to redact users/passwords.

It usually means you have a path mapped incorrectly. Post your docker run command. Be sure to redact users/passwords.

Just installed update. All looks good so far.👍

Wish I was in the EU.☹️

If you decide you want to troubleshoot later post your supervisord log as well as your docker run command. Please stop the container and delete the old supervisord.log so that a fresh one will get created on start. You should redact any users/passwords before posting.