![]() ![]() I can't figure out what's wrong but I can't really continue until I get this figured out. The port 32xxx you mentioned is QB's port with the router/NAT translator to the great Internet. Looking at the SSHD_config file, pubkeyauthentication is set to yes, passwordauthentication is set to yes, challengeresponseauthentication is set to no, permitrootlogin is set to yes. First the QBittorrent WebUI is a local service running and responding to connections on port 8080 NOT any other port like 32xxx like yours. I tried deleting my OMV standard user, making a new one from scratch from the Debian command line, again I can login to it just fine on Debian, but if I try to login from SSH I get access denied. I can login to either no problems through the NAS directly, and I can login to root from SSH, but I can't login to my standard user from SSH, it just gives me access denied. I was using the debian shell with SSH on root, I made a new user within the OMV webUI. ![]() I don't think I technically had one setup. Ran into some wonky business with standard user. Sorry for the pile of questions, once I get it up and running this will all make more sense to me, there is a lot of potential ambiguity for me though still at this point. ![]() Making the folder using that command places it in the root directory, correct? That cd command would work globally because it's just basically root/qbittorrent but root is omitted automatically? For the copy and paste, you are suggesting the one from the docker-compose section of the linxserver/qbittorrent page not the one from the docker CLI section? Do you need a separate application or plugin to use docker-compose or is that functionality built into the standard version of docker? Also would I need to launch the container every time I boot up the NAS or would it be booted automatically? Alles anzeigenīy standard user you mean the non-admin debian linux user? I made a different user inside of OMV, it gets kind of confusing which is which. Launch the container with docker-compose up -dĬheck that your container is running on Portainer GUI. Make and edit a file named docker-compose.yml: nano docker-compose.ymlĬopy/paste the sample from github editing the values to match your path.Ĭtrl+O, Enter and then Ctrl+X to save and close the editor. Usually this will be something like linuxserver/qbittorrent or linuxserver/qbittorrent:latest for the latest release. More information about the port can be found on the FreshPorts website. Near the top will be a 'Repository' setting containing the the path to image you are currently using. qBittorrent is officially packaged for FreeBSD. Make a folder named qbittorrent: mkdir qbittorrent Go to the Docker tab on your unraid server, click the icon for the qBittorrent container and pick 'Edit'. OK.On the web Gui, add you standard user to the docker group. So it would appear to be specific to the externalized /cache volume mapping, or Synology’s Docker implementation. ĭrwxr-xr-x 1 abc users 0 Aug 20 11:41 qBittorrent cacheĭrwxr-xr-x 1 abc users 22 Aug 20 11:41 dataĭrwxr-xr-x 1 abc users 80 Aug 20 11:52 ls -al /config/.cache/ĭrwxr-xr-x 1 abc users 68 Aug 20 11:45. bash_historyĭrwxr-xr-x 1 abc users 22 Aug 20 11:41. I created a clone and removed the /config mapping so it would use its own internal storage for /config… and it works! Of course the configuration won’t survive a container clear since its not externalized, but it does confirm that the error message is indeed referencing the correct directory: docker exec -it qbittorrent-copy ls -al /configĭrwxr-xr-x 1 root root 258 Aug 20 11:41. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |