chancedonmillion

I was running into the same issue. Docker Version "not available" In my case Fix Common Problems plugin was reporting "Unable to communicate with GitHub.com". This issue surfaced after setting unbound Pi-hole as the DNS on my home network. My workaround was as follows. 1. disable VM and docker in unraid settings 2. change the DNS in unraid IP settings to 1.1.1.1 (use whatever DNS you'd like) rather than my home router IP / Pi-hole 3. re-enable VMs and docker in unraid settings 4. toggle advanced view and force update containers in the docker tab of unraid After the following the above steps all contains show as up to date and are auto updating again.

likewise sh-5.0# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=25.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=25.7 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=26.1 ms ^C --- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 25.713/25.957/26.145/0.147 ms sh-5.0# ping goolge.com ping: goolge.com: Temporary failure in name resolution

I noticed that my qBittorrent web UI was down so I came to this thread and saw the discussion regarding the "cannot allocate 4611686018427387903 bytes" issue. I tailed the containers logs and sure enough, that is what I was seeing. 2020-03-30 20:49:11,570 DEBG 'start-script' stderr output: pgrep: cannot allocate 4611686018427387903 bytes I upgraded to the latest which fixed the "cannot allocate 4611686018427387903 bytes" issue. However the container is still failing to start. This is what I am seeing at in the logs currently. 2020-03-30 21:13:47,329 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=adb8c2b559fdde17f847119ecdeb1c8fda5b852953313e0488ef16f2bdb45a52... 2020-03-30 21:13:47,429 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 56 from curl != 0 [info] 12 retries left [info] Retrying in 10 secs... ... 2020-03-30 21:15:38,565 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 56 from curl != 0 [info] 1 retries left [info] Retrying in 10 secs... 2020-03-30 21:15:48,670 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx, exhausted retries exiting script... 2020-03-30 21:15:48,670 DEBG 'start-script' stdout output: [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port... Google tells me that code 56 is known to occur when the network adapter has a conflict with the third-party VPN installed on your system. I would really appreciate any insight as to why the adapter has a conflict with the third-party VPN and what I may be able to do as a workaround. I also tried deleting the image and reinstalling the container, same issue.

Thanks!

Can anyone point me towards documentation and/or examples of how to use the "Supported parameters" of the "Run external program on torrent completion" option in qBittorrent? The documentation on the qBittorrent GitHub wiki is pretty sparse regarding the subject. What I’m trying to accomplish is this. I would like to copy completed torrents from my "/mnt/user/downloads/complete" directory to either "/mnt/user/media/movies" or "/mnt/user/media/shows" using the category parameter specified when adding a torrent to the client. Also, I plan on using a bash script, where in the file structure of the container should I keep the script that I’ll be referencing?