dsmith44

DO NOT USE - SEE FIRST PAGE This docker container is deprecated This is now fixed, but this is the last ever update. SIX MONTHS FROM NOW DOCKER HUB IMAGES WILL BE REMOVED

I realise I am not the first person to post on this topic, though I've done quite a bit of work to narrow down where my issue is, and found an almost complete solution, so perhaps this will be helpful to others. ----------------------------------------------------------------- I recently upgraded to 10G networking between Unraid and my PC. Unraid is running on Proxmox ( Ryzen 5900X 128GB Ram ) as a 12 Core - 32GB VM. Direct pass through of 2x1TB Western Digital NVME and HBA for drives. Cache on NVME drives is a zpool mirror. VirtIO networking. PC to Unraid - iperf3 - 9.4Gb/s all day every day. Tick, network is working fine. Jumbo frames and I will get to 9.8Gb/s. This is testing from a WSL instance on PC to Unraid VM. Given virtualisation at both ends I am very happy with this and does a good job of validating everything is running nicely. Unraid onto cache NVMe drives tested with fio gives 200-2000 MB/s performance, average 1200 MB/s. Perhaps a bit lower than native drives but that's fine. This is also using fuse so excludes that as a cause I would think. Saving files to a cache share using Samba and it'll max out at about 480MB/s, which on the face of the the other tests I would hope to get closer to full wire speed. It's very stable at 480MB/s. smbd seems to top out at 70% of one core, so as single thread on that basis I perhaps could expect 700MB/s or so at max anyway. I was going to end my post with the following lines but then I had one final idea. I checked the CPU governor mode on Proxmox, I vaguely remembered setting it to powersave. I changed this back to performance using echo "performance" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor If you aren't running in a VM you can now set this in the settings page in version 7. This instantly increased throughput to 800MB/s ! The ondemand governor also performs similarly, and that's what I'm going to leave it on, don't need to be running at full speed when there is nothing to do. At that point I'm reasonably happy, unless anyone has any ideas for the last 200MB or so.

@EDACerton has suggested to me that his template that uses the official docker container becomes the replacement for my container. I think this is a good idea, and thank you. We'll work together to test/document cut over and then I'll update the instructions for this to reference his.

Hello everyone. At this point I want to step back from supporting this docker container, I don't use it personally at all. That was clear with the recent update that I just pushed without testing it at all, sorry but as I said I don't use this and have no interest in it anymore. For 99%+ of people the plugin is better and should be used. For the 1% of people doing odd things, you have some choices to make. Some of you take over the management of this, it's easy, run a script, push to docker hub I'l work with you and good folk at Unraid on how to best manage the transition as I have no idea You individually use the script to build your own images Something else - ideas on a postcard I'm going to put a date of the end of June for the last updates I will push to this, so after that unless someone wants to pick this up it will go stale at that point.

Please use the plugin instead. This is only for specialist use cases now.

1.64.0 == 1.64 == latest

Please check that the plugin isn't a better fit for you. This is only really for specialised use cases at this point.

1.62.1 = 1.62 = latest

1.60.1 = 1.60 = latest

latest = 1.58.2 = 1.58

This is the support thread for the docker container not the plugin. I think you want to be here http:// /topic/136889-plugin-tailscale/

1.58.2 == 1.58 == latest

latest == 1.56.1 == 1.56 is now available

At this point @plantsandbinary I would stop using this and install the plugin instead. This is really for special used cases using docker and private networks only now. I would also try using ip addresses only to exclude dns issues in the first instance for troubleshooting. Sent from my iPad using Tapatalk

1.54.1 has been pushed and latest updated to this version