- Create separate entry for DNS server settings, which can be changed at all times (user is not required to stop the array)
- Added "info" button which shows a popup window with interface related assignments (error is shown if something is missing)
- Added "show" button to show or hide VLAN settings
- Make network settings a tabbed view
- Fixed a bug when sometimes DNS settings are not properly set
- Fixed a minor bug in routing table content
- Some other code optimizations
- Support Precision Time Protocol (PTP) - time accuracy in nanoseconds
- PTP requires a local time server which supports the PTP protocol
- Show only the applicable fields for the selected time sync value (animated)
- Add 'hints' to help the user in configuration
- Do not restart time service when only date/time format is updated
Note for Tom: to make PTP work the package "linuxptp-4.2-x86_64-1_BW.txz" needs to be installed with stock Unraid
The MTU needs to be set to at least to the wireguard default. While it seems to work just fine, to create a docker bridge with a MTU of 1500, it breaks in some cases. For example, if you "curl https://api.minecraftservices.com/publickeys" via a container thats running over that wireguard-docker-bridge, it fails.
- Remove exclusion from share directory from .gitignore
- Add Unraid specific container hook script
- Add Tailscale icon
- Add helptexts for Tailscale
This integration allows users to easily make use of Tailscale in their Docker containers by just clicking a switch on the Docker page.
The Tailscale plugin itself is not needed for this integration but for the best user experience it is strongly recommended to install the Tailscale plugin from Community Applications.
How this works:
1. Configure Tailscale in the Docker template in Unraid and click Apply
2. Unraid will extract the default Entrypoint and CMD from the container
3. The hook script will be mounted in the container to /opt/unraid/tailscale-hook and the Entrypoint from the container will be modified to /opt/unraid/tailscale-hook
4. The original Entrypoint and CMD from the container, alongside with the other necessary variables for Tailscale will be passed over to the container
5. When the container starts the hook script will be executed, install dependencies (currently Alpine, Arch and Debian based containers are supported), download the newest version from Tailscale and run it
6. After the first start with Tailscale the container will halt and wait for the user to click on the link which is presented in the log from the container to add the container to your Tailnet
(alternatively one could also open up a Console from the container and issue `tailscale status` which will also present the link to authenticate the container to your Tailnet)
7. The hook script will pass over the default Entrypoint and CMD which was extracted in step 2 and the container will start as usual
These steps will be repeated after Container update, force update from the Docker page and if changes in the template are made.
If the container is only Started/Restarted the hook script will detect that Tailscale is installed and only start it, if one wants to update Tailscale inside the container simply hit `force update` on the Docker page in Unraid (with Advanced View Enabled)
The integration will show a Tailscale icon on the Docker page for each Tailscale enabled Container and show some basic information from the container (Installed Tailscale Version, Online Status, Hostname, Main Relay, IPs, Exit Node, Auth Expiry,...)
When Serve or Funnel is enabled it will also generate `Tailscale WebUI` in the drop down for the container which you can open up if Tailscale is installed from the device you are accessing Unraid.
bergware