possible breakage during the switch over - im testing this right now and will be trying my hardest to not break any existing configuration, the aim of this is for you not to really notice the change, until of course you attempt to use the env vars to change your endpoint and discover it no longer does anything :-) (see below)Ģ.
It does of course come with a couple of disadvantages:-ġ. No re-creation of Docker container - whilst this isnt a hassle for unraid users as we have a web ui (dynamix) to do this for us, for other users this is a big hassle, being able to switch endpoint by simply dropping in a new ovpn file is actually more convenient. changes to port and/or certs wont break the image - currently i bake in the PIA ovpn file and cert, whilst this is convenient for the end user it also means any changes to either of these files breaks the image, thus a decision to push the responsibility of this back to the user is another reason to drop env vars.Ĥ.
#Sabnzbd cannot create final folder download
less chance of mismatched configuration for endpoints - for certain vpn providers they require different ovpn options depending on the endpoint your connecting to, this will reduce this happening by forcing the user to download the correct ovpn file from the provider.ģ. less for the user to get wrong - if there are less env variables then hopefully there will be less chance of misconfiguration, im still seeing a fair bit of this happening.Ģ. Hi guys, so an important change is coming to this VPN docker image (and others in time - staggered change), in short i will be dropping the ability to configure the remote endpoint, tunnel device type, port, protocol and strong certs, instead the image will parse the ovpn file and use the values from the ovpn file.ġ. What are the preferred,generic permissions for docker/sab/sonarr/media folders etc? Can the dockers run as nobody, or root (dangerous?), etc? I always get confused on this point, unix vs smb permissions, and I often have problems deleting files from certain shares as my username, usually having to log in from the command line as root to delete. Permissions hadn't changed when the errors began, however now, of course, with all of my attempts to correct it, I've tried various permission changes here and there to no avail.įirst question: will running "new perms" on a system with dockers effect anything adversely? I am the primary user in the house, so of course my username is associated with nearly everything on the servers. Thus sab and sonarr will continue to need the unassigned devices mapping to the old server. In the meantime I would like to continue to get media downloading that media is stored on the old server that is being decomissioned. I am in the process of moving my media to a new server, but its going to take about a week to transfer it over the network. I can rebuild all of it if necessary, or at least the sab/sonarr part. The only dockers I am running are sab, sonarr, and plex. I am half tempted to just start over from scratch. Ok so i would dig more into the permissions being set via the unassigned disks plugin (something ive never used) also look to see if permissions can be set at the mount point and what the permissions are on the source file system, is /mnt/disks/192.168.0.4_tv_shows/ really set to user 'root' group 'root' as per your ls -al output?. Thus, I can't even retrieve the files from the download or working folders and move by hand. So sab not only cannot unpack, but it nukes all of the working files even though the unpack failed. Meanwhile, the downloaded file, unpacked files, etc (all of which appear to happen without issue) are nowhere to be found, anywhere, they literally are gone. Moreover, the file downloads, unpacks, and then the log shows the permissions error. Despite all attempts, I cannot change the mount point (the sab docker container mounts local "/mnt/disks/192.168.0.4_tv_shows" as its "/mnt/tv_shows" folder) permissions.ĭespite 777 permissions, sab still can't seem to write to this folder. ĭrwxrwxrwx 2 root root 0 Jun 28 19:16 192.168.0.4_tv_shows/ĭrwxrwxrwx 5 nobody users 114 Jun 25 04:43 chown bob:users ls -alĭrwxrwxrwx 5 nobody users 114 Jun 25 04:43 am using user "bob" to mount via SMB 192.168.0.4/tv_shows remotely, using unassigned devices. Drwxrwxrwx 4 nobody users 80 Jun 28 18:07.
0 kommentar(er)
