I am a noob with this but I did spend a lot of time on it before asking here. This was my first docker experience and I think I read too many guides and watched too many videos and at some point became confused. On your Docker Page, in the upper window (Docker Images), what do you have under Repository.?Īlso, if you're creating files and folders from your PC the PC user needs at least write on OMV. That's a kernel mode PID for swapper or shed, for paging. Why would you set PID (process ID) to 0? I had to look that up. Once a container is working like it should, it's best to leave it alone. In any case, once it's running correctly, you could add paths (carefully). I'm guessing the additional paths you had in your container were a result of configuration inside of sabnazbd. The host path side of the following is my preference but it would work for you if you want to use it. The rest of the environ variables are defaults.įrom gderf's advice, put a / in the Container path and choices come up. The PUID (1000) is for my first user and the PGID (100) is for the default "users" group. ![]() In bridge mode, they're 1 to 1 and self populate. Scroll through.)ĭon't worry about the ports. (This is 3 captures of the run image dialog. In any case, the following is what I have for a configuration. I don't have a usenet account so I couldn't fully test the Docker. ![]() I believe I set those values to 0 to solve an earlier problem. Here is what I have for the docker settings. Sickbeard (another docker) has no problems renaming these folders. Yes, it is a new setup but I don't recall the rename ever working. To be honest I had trouble getting the docker set up correctly as this is all new to me. Maybe the docker (which is on a different host) has the issue and is thus polluting the access of the newly-created folder? I assumed that because I have the same permission issue hitting that folder from my pc that the issue was in the shared folder setup. Thanks so much for your response! It had not even occurred to me that the issue was the docker itself. This is the most popular sabnzbd docker on the hub and it's well documented. If this particular sabnzbd docker doesn't work for you, try another. On the destination (receiving) folder, don't alter permissions until you've done a few tests to be sure the docker is working correctly. The bottom line? Go over the dockers configuration with a fine toothed comb. Third would be examining the setup of this particular docker, against the authors recommended setup, as it's laid out on the Docker Hub. Second, would be taking a look at the volumes and mount points for the docker. First, the docker may need a UID or GID set in its configuration. What I would look at first is the sabnzbd docker itself. You're assuming that this is a permissions related problem when, in fact, it may be a configuration item in the Docker itself. Growth of this folder is normally limited to 5 MB.The first question I'd ask, is this a new setup or has this configuration worked before? Altough only needed for troubleshooting, you must have this folder. ~/Library/Application Support/SABnzbd/admin %userprofile%\AppData\Local\sabnzbd\admin Used for the internal administration of the job-queue and history. You want to put this on a volume with plenty of room. Each job is placed in a separate folder, named after the NZB file that started it. Here all completed download jobs are stored. ![]() There should be enough space to contain the largest complete job + 10% for error correction data. When complete, the data is moved to the complete_dir. Here SABnzbd collects the data for each download and error correction (par2) is done. ~/Library/Application Support/SABnzbd/sabnzbd.ini %userprofile%\AppData\Local\sabnzbd\sabnzbd.ini ![]() However, the path must be accessible to SABnzbd when it is launched otherwise it will be reset to the default path.Ĭonfiguration file sabnzbd.ini Operating System NOTE You can set fixed paths such as D:\Downloads, or /Volumes/nameofdrive/Downloads. The download_dir, complete_dir, dirscan_dir are relative from the current users home directory. NOTE The paths of the log_dir, admin_dir will be relative to the location of the sabnzbd.ini file unless a fixed path is set. The expression %userprofile% is for Windows your personal folder in C:\Users\ which can be directly entered in Run ( WindowsKey+R).įor Posix (Linux) ~ means your home folder. The following table explains the purpose of each folder, its default location and its keyword in the INI file.Īll folders can also be changed through the Web-GUI. Given that some folders can become very large, you may want to relocate them. SABnzbd uses a number of folders for different purposes, some are just for internal administration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |