JNCK

Hi! I want to run this NodeJS application for 24/7 on my server, but it doesn't offer a Docker container option. Preferably I run it in a Docker container so my Unraid installation is kept as clean as possible. But how can I achieve this? It's this GitHub project: https://github.com/Achaak/toogoodtogo-bot I looked for an empty, barebones, NodeJS docker container to do the 'git clone' in and build + run the application. Who is able to help me? Thank you!

Hi! Since using Sonarr and Sabnzbd I'm experiecing very slow import times. I've setup the /data folders of Sabznbd and Sonarr exactly the same and Sonarr can find the download files just fine, but only the import is very slow. It looks like it's reading the files at ~ 30 MB/s and after a few seconds writing at the same 30 MB/s. This makes the whole downloading process of a series slow (especially when having a 1 GBit/s internet connection). The destination folder of my series in Sonarr is a MergerFS folder located at /data/mount_mergerfs/TV/, but it' still inside the same folder range Sonarr and Sabnzbd have access to (local: /mnt/user/, Container path: /data). The MergerFS folder has a local folder on the same NVMe SSD. So I think this shouldn't be the bottleneck. Thanks for helping!

All the container I route through passthroughvpn become unreachable. I can restart only one Docker container that uses passthourghvpn and then only that Docker container works for around 20 minutes. All other container that just use my normal network just work fine. Only the containers that use passthroughvpn are affected. Thanks! Verzonden vanaf mijn iPhone met Tapatalk

I’m having issues with Docker containers becoming unreachable after 20 minutes or so [mention]Dyonr [/mention]. I have a post about this here: https://r.tapatalk.com/shareLink/topic?share_fid=18593&share_tid=104249&url=https%3A%2F%2Fforums%2Eunraid%2Enet%2Findex%2Ephp%3F%2Ftopic%2F104249-Docker-containers-become-unreachable-after-20-minutes&share_type=t&link_source=app I can’t solve it

I’m routing it through passtroughvpn of [mention]Dyonr [/mention]. I’ll post this in his support thread.

Anyone who may be able to help me with this issue? Thanks!!

Hi! I have issues with Docker containers becoming unreachable. I have multiple containers that are connected to a passthroughvpn container to route the traffic through my VPN. After 20 minutes or so all of the containers that use the --net=container:passthroughvpn parameter become unreachable. In the system logs I see the following happening at that exact moment: Mar 16 14:01:34 Tower kernel: docker0: port 1(vethacf7621) entered disabled state Mar 16 14:01:34 Tower kernel: veth2a56a85: renamed from eth0 Mar 16 14:01:34 Tower avahi-daemon[6570]: Interface vethacf7621.IPv6 no longer relevant for mDNS. Mar 16 14:01:34 Tower avahi-daemon[6570]: Leaving mDNS multicast group on interface vethacf7621.IPv6 with address fe80::c4cf:59ff:fe78:fc30. Mar 16 14:01:34 Tower kernel: docker0: port 1(vethacf7621) entered disabled state Mar 16 14:01:34 Tower kernel: device vethacf7621 left promiscuous mode Mar 16 14:01:34 Tower kernel: docker0: port 1(vethacf7621) entered disabled state Mar 16 14:01:34 Tower avahi-daemon[6570]: Withdrawing address record for fe80::ffff:59ff:fe78:fc30 on vethacf7621. Mar 16 14:01:34 Tower kernel: docker0: port 1(vethd3ac1eb) entered blocking state Mar 16 14:01:34 Tower kernel: docker0: port 1(vethd3ac1eb) entered disabled state Mar 16 14:01:34 Tower kernel: device vethd3ac1eb entered promiscuous mode Mar 16 14:01:34 Tower kernel: docker0: port 1(vethd3ac1eb) entered blocking state Mar 16 14:01:34 Tower kernel: docker0: port 1(vethd3ac1eb) entered forwarding state Mar 16 14:01:35 Tower kernel: docker0: port 1(vethd3ac1eb) entered disabled state Mar 16 14:01:35 Tower kernel: eth0: renamed from vethc37dad7 Mar 16 14:01:35 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd3ac1eb: link becomes ready Mar 16 14:01:35 Tower kernel: docker0: port 1(vethd3ac1eb) entered blocking state Mar 16 14:01:35 Tower kernel: docker0: port 1(vethd3ac1eb) entered forwarding state Mar 16 14:01:36 Tower avahi-daemon[6570]: Joining mDNS multicast group on interface vethd3ac1eb.IPv6 with address fe80::e040:1bff:feac:bbcd. Mar 16 14:01:36 Tower avahi-daemon[6570]: New relevant interface vethd3ac1eb.IPv6 for mDNS. Mar 16 14:01:36 Tower avahi-daemon[6570]: Registering new address record for fe80::ffff:1bff:feac:bbcd on vethd3ac1eb.*. A Docker container that is using --net=container:passthroughvpn becomes reachable again when I restart that specific container. After again around 20 minutes the container isn't reachable anymore. I've searched online and I scrubbed my Docker and also increased the vDisk size to 50 GB for Docker. Still this issue persists. Maybe someone knows what the above system logs mean? Thanks! tower-diagnostics-20210316-2207.zip

Hi @Dyon It seems like I've fixed it and it had nothing to do with your Docker container, I'm sorry about that. The Plex issue was fixed by setting up a route in my network, so my devices are able to access the Docker container IP. The Sonarr issue was fixed by setting up Sabnzbd and Sonarr so they both have in the container a /data folder and both are pointing to /mnt/user/. I found this solution here: https://www.reddit.com/r/unRAID/comments/knl0tp/how_to_start_troubleshooting_slow_transfer_speeds/

Thanks for helping! I have this same issue with Radarr that’s routed through passthroughvpn where the import from the local SABNZBd to the local media folder also seems to cap out on my maximum upload speed. It seems like to container is sending the file to the VPN and then getting it back again? Very weird. The above makes the importing proces after a successful download very slow Verzonden vanaf mijn iPhone met Tapatalk

Yes, this is what I'm seeing. My server Unraid server is on IP 192.168.2.11. I can access Plex using 192.168.2.11 : 32400. When I'm playing back 4K media using one of my devices on the 192.168.2.0/24 network it's not streaming the file using the local network, but is pulling the stream from the VPN (I've opened port forwarding there). I can confirm the above, because when I'm playing back a large file Netdata is showing a high upload and doing an upload speedtest with Speedtest.net is very slow at that same moment. My devices in the local network are pulling the stream from the VPN instead using a local route. Can really find a solution for this

I'm using this container for Plex, but I'm having issues that local playback still goes through the VPN. In the Plex dashboard it tells me the stream is 'Remote' and I can almost certainly confirm this because I can't local playback Remux 4K streams directly, becuase the download tops at my maximum upload speed of my internet speed. How can I fix this? I already pointed the Plex port so I can access the Plex server internally using the IP of my Unraid server + Plex port. In the Plex installation I do still see the local 172.17.0.4 : 32400. Thanks for helping!

Hi! I'm experiencing very slow import speeds. I have Sonarr and Sabnzbd pointed to the same local download folder and Sonarr has to move files to a other local folder on my server. I'm seeing this kinds of speeds: At some points the 'Disk Write' spiks to 500MiB/s. Does anyone know how to fix this? I'm using a Samsung 970 PRO NVMe SSD for the local files, nothing else, so this should be very fast. Thanks!

What should I do? Verzonden vanaf mijn iPhone met Tapatalk

Hi everyone! I'm getting this error in Sonarr when selecting a specific episode to download: BlacklistSpecification: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct. Thanks!

Hi! I'm using the AdGuard Home container but experiecing very slow resolving times compared to just use 1.1.1.1. It seems like AdGuard Home isn't caching my requests and there is something causing these slow resolving times. Anything I should check?