fix: add --retry 3 to bun install in Dockerfile
Docker build steps (builder, test-runner, runner stages) also run bun install and suffer the same transient tarball extraction failures as the workflow steps.
This commit is contained in:
+3
-3
@@ -13,7 +13,7 @@ WORKDIR /app
|
||||
COPY package*.json ./
|
||||
|
||||
# Install dependencies (including dev dependencies for building)
|
||||
RUN bun install
|
||||
RUN bun install --retry 3
|
||||
|
||||
# Copy source code
|
||||
COPY . .
|
||||
@@ -39,7 +39,7 @@ WORKDIR /app
|
||||
COPY package*.json ./
|
||||
|
||||
# Install ALL dependencies (including dev dependencies for testing)
|
||||
RUN bun install
|
||||
RUN bun install --retry 3
|
||||
|
||||
# Copy source code
|
||||
COPY . .
|
||||
@@ -68,7 +68,7 @@ COPY --from=builder --chown=euchre:euchre /app/bun.lock ./bun.lock
|
||||
COPY --from=builder --chown=euchre:euchre /app/prisma ./prisma
|
||||
|
||||
# Install only production dependencies
|
||||
RUN bun install --production
|
||||
RUN bun install --retry 3 --production
|
||||
|
||||
# Generate Prisma client
|
||||
# Note: We need to set DATABASE_URL even for generation because prisma.config.ts requires it
|
||||
|
||||
Reference in New Issue
Block a user