The best solution is to use a single, common volume Some also recommend paths for the download client container that are different from the Radarr container, like This causes slow moves and doesn't allow hard links because theyĪre considered two different file systems Both problems can be solved with well planned, consistent paths. The second is a performance issue and causes problems for seeding torrents. torrents/My.Movie.2018/, but in the Radarr container that might be at The first is a problem because the download client will report a download's path as There are two common problems with Docker volumes: Paths that differ between the Radarr and download client container and paths that prevent fast moves and hard links. Radarr v4 will convert the given directory on startup if a Radarr v0.2 or v3 database is found. Restarting the NAS using the Web UI causes the issue.Volume to mount the data directory and supply that path to Radarr as parameter. Possibly file permissions? Restarting the containers do not cause any issues. Ok, I looked at it more and my current YAML files should properly follow these steps, and all files on the containers have bind mounts that map to folders on the NAS so I don't know exactly what is causing the issues. You can always manually edit the files from the NAS filesystem, but it will be necessary to restart the container for the changes to take effect. Changes made to the configs will then vanish if the container is restarted. IF, once you have your applications configured the way you want, you do NOT want them modified from inside the app, you can change the rw to ro. After making the change to the docker-compose file, do a docker-compose restart on the container.your configs SHOULD be persistent. The rw is important if you want to be able to update those configs from INSIDER the container. path/to/file/on/NAS:/path/to/file/in/container:rw Here are the current YAML files with some details changed for security reasons (directory names, VPN credentials, IP's and Port #'s) I am not sure what the cause of these issues are so I am hoping someone with a little more knowledge can help me diagnose and fix the above issues. Prevent the qBittorrent settings from being reset during the reboot. ovpn file from being deleted during the reboot process.ģ. Fix the “Failure Unauthorized” and “Failure Unable to retrieve environments” errors and get it so that I don’t have to re-add a new admin account.Ģ. The main things I need help with fixing are as listed:ġ. Once rebooted I can load qBittorrent but it has all the default settings and they must be reconfigured. ovpn file used by qBittorrent is gone/deleted and I must re-add it to the mapped config folder and reboot qBittorrent. The container for all the apps are still present and those settings are untouched.Īfter the NAS reboot the. It asks me to create a new admin user and then lets me in. Portainer upon loading shows two errors on the top right: “Failure Unauthorized” and “Failure Unable to retrieve environments” Upon rebooting both qBittorrent and Portainer seem to reset most settings. Upon restarting the NAS both Portainer and BitTorrent try to start, but with issues. Everything runs smoothly until I decide to reboot the NAS. I am able to properly install PortainerCE and qBittorrent using docker compose with a Yaml file (using container station or through SSH). yaml) and qBittorrentVPN (Intsalled using Docker Compose. I have had an annoying issue using Portainer-CE (Intsalled using Docker Compose.
0 Comments
Leave a Reply. |