Repository navigation
Conversation
T3 Code requires a relay client >= 2026.10.3 and rejects the image's 2026.5.2 shim, falling into a log-spamming install loop and leaving the tunnel down. Pin 2026.11.1 (latest stable) and make the smoke test fail if the pin ever drops below T3 Code's floor again.
0libote
added a commit
to 0libote/t3code-docker
that referenced
this pull request
Nov 21, 2026
0.1.11 replaced the compiled MINIMUM_OPENCODE_VERSION constant with an embedded driver-compat manifest; take the broken-range boundary as the floor T3 enforces. 1.14.19 stays the floor, so the catalogue and the installed 1.19.6 still meet it. Also carry the cloudflared 2026.11.1 bump from dizys#153: the newer bundled runtime enforces its 2026.10.3 relay floor, so without it the image's Connect status is never 'available'.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
T3 Code containers built from this image spam their logs (~645 lines per 15 minutes on a live deployment) with an endless loop of:
ERROR: T3 Connect is NOT reachable from other devices — The tunnel client (cloudflared) is not runningWARN: T3CODE_CLOUDFLARED_PATH must point to cloudflared 2026.10.3 or newer…and the relay tunnel never starts, so the machine is unreachable from other devices.
Why it happens
After the October 2026 Cloudflare certificate compromise, T3 Code requires a relay client ≥ 2026.10.3 and checks the version reported by the executable at
T3CODE_CLOUDFLARED_PATH. In this image that path is the on-demand shim, whose--versioncomes from the build-time catalogue (/opt/t3-services/catalogue.json) — pinned to 2026.5.2 viaARG CLOUDFLARED_VERSION.Because the shim is the configured override, T3 Code also never falls back to downloading its own managed client. Both paths are blocked, so it retries forever and the error loop spams the logs.
The fix
ARGand theservice-catalogue.mjsgenerator default. No checksum changes needed — the catalogue sha256 is computed at build time from the downloaded bytes.cloudflared_matches_t3only compared the image against its own Dockerfile pin, which would pass for any stale version. It now also fails when the pin drops below T3 Code's 2026.10.3 floor, so this regression can't come back unnoticed.Validation
service-packages,connect,services-recovery).bash -nclean; floor logic verified:2026.11.1pass,2026.10.3pass,2026.5.2fails as intended.t3 connect statusreported the tunnel up (4 QUIC connections to the edge) and the log spam stopped.