hanzoai/team
2
0
Fork 0
mirror of https://github.com/hanzoai/team.git synced 2026-09-30 01:57:35 +00:00
Code Issues Releases Activity

Give the install a cache to resume from

Browse Source 
Rootless BuildKit puts a build step on slirp4netns, where an install that
takes three and a half minutes in a pod stalls at ten. Cached tarballs
keep each attempt short enough to finish.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-09-08 17:15:02 -07:00
co-authored by Hanzo Dev
parent 920ee9d100
commit eeaeaa31be
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Dockerfile
+8 -1
View File
@@ -37,7 +37,14 @@ COPY webapp .
# the same two repositories over the port that answers. It changes the transport
# and nothing else -- the lockfile still names the commit, and that commit is what
# git checks out.
RUN git config --global url.https://github.com/.insteadOf ssh://[email protected]/ \
# The cache mount is not only speed. The daemon is rootless BuildKit, so a build
# step's network is slirp4netns rather than the pod's: the identical `npm ci`
# finishes in three and a half minutes in a pod on this node and stalls on `read
# ETIMEDOUT` around the ten-minute mark inside a build step. Cached tarballs mean
# an attempt resumes where the last one reached instead of asking for all 1954
# packages again, so the install shrinks below the length that provokes it.
RUN --mount=type=cache,target=/root/.npm,sharing=locked \
git config --global url.https://github.com/.insteadOf ssh://[email protected]/ \
&& npm ci --no-audit --no-fund \
--fetch-timeout=60000 --fetch-retries=5 \
&& npm run i18n-extract:check && npm run build