- Ability to connect to a service using only funnel without running Services in the container
Full changelog
We now support using only funnel to connect to a service, without running any Services on that container.
Thanks for all the feedback 🙏
A Docker‑label‑driven tool that automatically exposes containers as Tailscale Services, eliminating the need to publish container ports.
We now support using only funnel to connect to a service, without running any Services on that container.
Thanks for all the feedback 🙏
IGNORE_SERVICE_NAMES to protect named svc: services from DockTail reconciliation cleanupfoo or svc:foo workssvc:e2e-manual-protected)First of all, thanks for all the feedback so far. Keep it coming! This feature came from a community request and adds the ability to publish a container as multiple different services at the same time through different ports. This can look something like this:
services:
gluetun:
image: gluetun:latest
labels:
- "docktail.service.enable=true"
- "docktail.service.name=qbittorrent"
- "docktail.service.port=8000"
- "docktail.service.1.name=bitmagnet"
- "docktail.service.1.port=8001"
This release makes it a lot easier and more secure to use DockTail for your setup. You're no longer required to publish ports to the host for the to be published as a Tailscale Service!
You don't need to change anything and legacy setups should continue to work the same as before. Refer to the ReadMe to see how to use it without port publishing.
Thanks for all the positive feedback in the last few weeks! 🎉
Stable release of DockTail - automatically expose Docker containers as Tailscale Services using label-based configuration.
Thanks to everyone who gave feedback and reported issues during early access!
See the README for setup instructions.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Beta — feedback welcome: [email protected]