https://brtkwr.com/tags/buildkit/Recent content in Buildkit on brtkwr.comHugoenTue, 27 Oct 2026 12:00:00 +0000https://brtkwr.com/posts/2026-10-27-why-docker-pushes-to-artifact-registry-time-out-at-60-seconds/Tue, 27 Oct 2026 12:00:00 +0000https://brtkwr.com/posts/2026-10-27-why-docker-pushes-to-artifact-registry-time-out-at-60-seconds/<h2 id="tldr"> TL;DR <a class="heading-link" href="#tldr"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>Our image pushes from GitHub Actions to Google Artifact Registry kept failing with <code>failed to authorize: DeadlineExceeded: context deadline exceeded</code>, always about 60 seconds into the push, and usually passing on a rerun. The 60 seconds is BuildKit&rsquo;s limit on how long it waits for the buildx client to hand back a registry token. The client asks Artifact Registry for that token with a POST first. Artifact Registry doesn&rsquo;t support it and answers 405, which normally takes 20ms, after which the client falls back to a GET that works. Occasionally the 405 reply never finishes, the client sits on it until BuildKit gives up, and the GET never runs. Setting <code>BUILDKIT_NO_CLIENT_TOKEN=1</code> where buildx runs makes BuildKit fetch tokens itself, and BuildKit tries GET first.</p>