<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Buildkit - 标签 - William</title>
    <link>https://williamlfang.github.io/tags/buildkit/</link>
    <description>Buildkit - 标签 | William</description>
    <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><lastBuildDate>Fri, 16 Oct 2026 14:03:28 &#43;0900</lastBuildDate><atom:link href="https://williamlfang.github.io/tags/buildkit/" rel="self" type="application/rss+xml" /><item>
  <title>docker buildx: the builder had a proxy, the client didn&#39;t</title>
  <link>https://williamlfang.github.io/2026-10-16-docker-buildx-anonymous-token-timeout/</link>
  <pubDate>Fri, 16 Oct 2026 14:03:28 &#43;0900</pubDate>
  <author>william</author>
  <guid>https://williamlfang.github.io/2026-10-16-docker-buildx-anonymous-token-timeout/</guid>
  <description><![CDATA[<p>My image build script started failing on its very first line, <code>FROM python:3.10</code>,
with <code>failed to fetch anonymous token ... TLS handshake timeout</code>. The odd part:
the buildx builder I use is created with a proxy for exactly this reason, and
from another shell the same build worked.</p>
<p><strong>The token request is not made by the builder. It is made by the <code>docker buildx</code>
client in your own shell, using your shell&rsquo;s proxy variables.</strong> My interactive
zsh exports none, so that one request went direct and timed out. Two <code>export</code>
lines in the build script fixed it.</p>]]></description>
</item>
</channel>
</rss>
