-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish Dockerfile to enable docker pull tailscale #295
Comments
I tried to register the "Docker ID" of "tailscale" on hub.docker.com but apparently it's already taken, but this is a 404: https://hub.docker.com/tailscale Do I not understand what a "Docker ID" is? This works differently than I remember doing this last. /cc @danderson |
The "tailscale" org already exists, and we own it :). We just haven't pushed any repos yet, so the hub's weird about showing anything. I created an empty tailscale repo, so https://hub.docker.com/r/tailscale/tailscale is visible now - albeit empty. |
Great. Want to invite me to push to it? https://hub.docker.com/u/bradfitz |
We're going to put this on hold until we have better container support (#504) |
In the mean time, (and for simple vanilla-docker use cases only) I wrote a balena service to test out for our edge nodes. It's been working great so far. |
I also needed to run this via Docker, as Flatcar (former CoreOS) can pretty much only run container workloads. I'm publishing Docker image for amd64 + ARM (Raspberry Pi etc.) here: https://github.com/function61/tailscale-dockerimage (edit: added multi-arch images) |
I think a few things are left to be done:
|
Or could tailscale itself maybe do this fallback? That would fix the problem in other environments without /dev/net/tun, too. |
Running with /dev/net/tun, tailscaled is a network interface supporting the usual socket programming paradigm. Running with userspace-networking, tailscaled is a SOCKS5 proxy which the application code has to be configured for. Applications which don't use SOCKS5, like even ping, don't work in userspace-networking mode. If the two modes were more transparent I think we'd automatically fall back between them, but the rest of the system has to be ready for the differences in the two modes. |
Tailscale 1.16 added http_proxy support alongside the existing SOCKS5 proxy support. |
We now publish an image on Docker Hub: https://hub.docker.com/r/tailscale/tailscale/tags Please let us know what else you'd need to make this better (feel free to open new feature requests!), e.g.,
|
And it's in GitHub Packages now too: https://github.com/orgs/tailscale/packages/container/package/tailscale |
As a totally lazy stay at home dev, a community application for unRaid would be very helpful. Beyond that I need to know what parameters I need to run (and if its none, I need to know what I well). I don't see anything at the docker hub. |
I'm going to close this issue as done, |
Any plans to publish multi-arch Docker images, e.g. ARM build? |
@joonas-fi Created a new issue for multi-arch Docker images, since this one is closed: #4856. It's easier for us to track upvotes on new issues rather than on comments. |
Is your feature request related to a problem? Please describe.
It's fantastic that this repo has a Dockerfile. It is frustrating to have to clone the repo to use it.
Describe the solution you'd like
Publish the image on Docker Hub to make
docker pull tailscale:tailscale
work.Describe alternatives you've considered
Self publishing from a fork? Seems like doing it from the source of truth is probably best.
Additional context
Issue requested by @bradfitz https://twitter.com/bradfitz/status/1249839926545281024?s=20
Front conversations
The text was updated successfully, but these errors were encountered: