Enhancement: allow container to work with tailscale plugin in Unraid 7 #5288
Replies: 1 comment 3 replies
-
Thank you for the detailed report regarding Tailscale integration with the LibreChat container. The current Dockerfile runs the application as a non-root user (node) as a security best practice to limit potential vulnerabilities if the container were to be compromised. This is especially important for applications handling API keys and user data. Is building the image yourself not an option? You could modify the Dockerfile locally to test the necessary changes for Tailscale support. If you do try this, it would be very helpful if you could share your working configuration - this would help us validate the exact changes needed for proper Tailscale integration. If building locally isn't feasible, I could consider adding a separate "-tailscale" tagged image that includes the necessary modifications while maintaining the current secure default image. This would allow users to choose between the standard secure configuration and a Tailscale-compatible version. Please let me know if you're able to test a modified build, or if you'd prefer to wait for an official Tailscale-compatible image. Your feedback would be valuable in determining the best path forward. |
Beta Was this translation helpful? Give feedback.
-
What features would you like to see added?
With Unraid 7's release, we can add tailscale serve to specific containers. This is working for most of my containers but not with your LibreChat container, which I gathered from the Unraid CA.
More details
Name = LibreChat
Repo = ghcr.io/danny-avila/librechat-dev:latest
Privileged = Off
Use Tailscale = On
TS Hostname = librechat
The rest are defaults other than my API keys and the like. When I apply it, docker run fires up the container, but the logs show tailscale not getting ran, because it runs into an error:
and it goes on and the container starts just no tailscale because "No root privs". I retried with privileged = On, but encountered the same error. Discussing this on another forum, someone suggested that the
USER
instruction in the Dockerfile (See here) is the problem here. In order to bypass this, you'd need to rebuild the container without that instruction.In case it is helpful to reproduce the issue, here is what my docker run output looks like:
Please let me know if I can provide anything further.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions