Tailscale's install script exits on Ubuntu 26.10 because its apt repo has no stonking directory
Tailscale's apt repo returns 404 for Ubuntu 26.10 ('stonking'), so the standard install script refuses to run on a fresh server. A DEV Community author reports the 26.04 ('resolute') repo works as a stopgap.
The Engineer · Build desk
Who a stonking 404 reaches. Install script users: it exits with status 1. Config templates: apt update fails with 404 Not Found. Scripts and cloud-init: apt update exits with status 100. Docker and HashiCorp repo users: the same 404. Teams on 26.10: resolute files installed Tailscale 1.104.1.
- What it limits constraint Tailscale install script users Script prints "ubuntu stonking isn't supported by this script yet." and exits with status 1, claim 4
- Who's exposed exposure Config management templates A template filling in stonking from OS facts makes apt update fail with 404 Not Found, claim 7
- What it costs cost Scripts and cloud-init runs apt update exits with status 100, so one missing vendor repo fails the whole update, claim 8
- What it sets up precedent Docker and HashiCorp repo users The author hit the same 404 in the 26.04 to 26.10 upgrade, and the fix was the same, claim 16
- What's now possible capability Teams installing on 26.10 Fetching the resolute key and list files installed Tailscale 1.104.1, with tailscaled enabled and running, claim 11
| Who | How | Kind | Claim |
|---|---|---|---|
| Tailscale install script users | Script prints "ubuntu stonking isn't supported by this script yet." and exits with status 1 | constraint | 4 |
| Config management templates | A template filling in stonking from OS facts makes apt update fail with 404 Not Found | exposure | 7 |
| Scripts and cloud-init runs | apt update exits with status 100, so one missing vendor repo fails the whole update | cost | 8 |
| Docker and HashiCorp repo users | The author hit the same 404 in the 26.04 to 26.10 upgrade, and the fix was the same | precedent | 16 |
| Teams installing on 26.10 | Fetching the resolute key and list files installed Tailscale 1.104.1, with tailscaled enabled and running | capability | 11 |
What happened
- The same Release URL under the 26.04 codename, resolute, returns 200, and Tailscale's package page lists 26.04, 25.10, 25.04 and older but no 26.10.
- On a 26.10 host the install script prints "ubuntu stonking isn't supported by this script yet." and exits with status 1.
- A source line naming stonking, hand-written or filled in by a config management template, makes apt update fail with a 404 and a missing Release file error.
- Fetching the resolute key and list files in place of the stonking ones, then running apt-get install, gave Tailscale 1.104.1 with tailscaled enabled and running.
Why it matters
- What it limits constraint The one-liner cannot be bent to 26.10. The script has no codename override, so teams add the repo by hand until Tailscale publishes a stonking directory.
- What it costs cost Automation that templates the codename pays more than a manual installer does. The failed update exits with status 100, so one missing vendor repo fails the whole update, not just the Tailscale part.
- Who's exposed exposure The test covers install and service start only. Joining a tailnet was not tested on 26.10, and the post leans on a 26.04 guide for those steps.
- What it sets up precedent Docker's and HashiCorp's repos returned the same 404 in the author's 26.04 to 26.10 upgrade. We'd expect any third-party source keyed on codename to need a check for a stonking suite.
The script reads the codename from /etc/os-release, which on 26.10 gives UBUNTU_CODENAME as stonking, and checks with the package server that the codename is supported before making any change to apt [3]. That ordering keeps the failure clean. The author found /etc/apt/sources.list.d/ still held only ubuntu.sources afterwards [5].
The apt failure is the one that costs time. The error text, "does not have a Release file", sounds like a broken repo. The author says the 404 Not Found on the Err line is the real message: that suite does not exist on the server [9].
According to the post, Tailscale itself has no problem on 26.10. The 26.04 repo's package runs without issue, and what is missing is a directory on the package server that every official install path looks up by codename [10].
A second route skips apt. The post says the static binaries plus the systemd unit in the tarball work too, and that tailscale update keeps them current [12]. Teams that do not want an apt source naming a codename the host is not running have that option.
The apt route leaves exactly that kind of source file. The author's trigger for undoing it is the installer-supported URL for stonking: when it says OK, replace resolute with stonking in /etc/apt/sources.list.d/tailscale.list [13]. We'd leave a comment in that file saying why it says resolute.
The evidence is one box. The author tested a fresh 26.10 server on kernel 7.3.0-9-generic, x86_64, on 16 October 2026, the day after release [14]. That dates the release to 15 October [17]. For the result to transfer, a host would need to match that setup: Tailscale 1.104.1 from the resolute repo on an x86_64 server. The post does not report other architectures.
What to watch
- The stonking installer-supported URL on pkgs.tailscale.com returning OK, which is the author's signal to change resolute back to stonking in tailscale.list.
- Tailscale's package page adding a 26.10 entry; it currently starts at 26.04.
- Whether Docker's and HashiCorp's stonking suites appear, since the author hit the same 404 with both.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence68
- Adoption
- Not scored
- Hype gap−5
- Incentives
- Not scored
- Confidence66
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Tailscale builds its apt repo per Ubuntu codename, and there is no stonking (26.10) repo yet; the stonking Release URL on pkgs.tailscale.com returns HTTP 404.
- [2]
The same Release URL with resolute (26.04) returns 200, and Tailscale's package page starts at 26.04, then 25.10, 25.04 and older, with no 26.10.
- [3]
The install script reads the codename from /etc/os-release (UBUNTU_CODENAME=stonking on 26.10) and asks the package server whether that codename is supported before it touches apt.
- [4]
For stonking the server answers with a 404, and the install script prints "ubuntu stonking isn't supported by this script yet." and exits with status 1.
- [5]
The script stops before writing anything: /etc/apt/sources.list.d/ still held only ubuntu.sources afterwards.
- [6]
There is no flag to make the install script use another codename; it takes TRACK and TAILSCALE_VERSION, neither of which helps.
- [7]
An apt source that names stonking, whether the deb line was written by hand or a config management template fills the codename in from OS facts, makes apt update fail with 404 Not Found and the error that the repository does not have a Release file.
- [8]
Both apt update and apt-get update exit with status 100, which matters in a script or a cloud-init run: one missing vendor repo fails the whole update, not just the Tailscale part.
- [9]
The author says the 404 Not Found on the Err line is the real message, meaning that suite does not exist on the server; 'does not have a Release file' sounds like a broken repo but is not.
- [10]
The author says nothing is wrong with Tailscale on 26.10: the package from the 26.04 repo runs fine, and what is missing is a directory on Tailscale's package server, which every official install path looks up by codename.
- [11]
The tested fix is to fetch resolute.noarmor.gpg and resolute.tailscale-keyring.list instead of the stonking ones, then run sudo apt-get install tailscale; it installed Tailscale 1.104.1 on 26.10 and tailscaled came up enabled and running.
- [12]
To keep apt out of it, the static binaries plus the systemd unit in the tarball also work, and tailscale update keeps them current.
- [13]
When https://pkgs.tailscale.com/stable/ubuntu/stonking/installer-supported says OK, swap resolute for stonking in /etc/apt/sources.list.d/tailscale.list.
- [14]
The author tested on a fresh Ubuntu 26.10 server (kernel 7.3.0-9-generic, x86_64) as a sudo user, on 16 October 2026, the day after release.
- [15]
The author could not test joining a tailnet from the lab, and points to a 26.04 Tailscale guide for the post-install steps (auth keys on a headless box, MagicDNS, exit nodes), which use the same commands.
- [16]
The author hit the same 404 with Docker's and HashiCorp's repos in the 26.04 to 26.10 upgrade, and the fix was the same.
- [17]
Ubuntu 26.10 was released on 15 October 2026.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toInstall Tailscale on Ubuntu 26.10
1 article · October 16, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.