Skip to content

chore: use Node.js 22 and fix corepack installation #10746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 11, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 6 additions & 8 deletions packages/proxy-container/Dockerfile
Original file line number Diff line number Diff line change
@@ -1,17 +1,15 @@
FROM node:18-alpine AS base
FROM node:22-alpine AS base

ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"

RUN apk update
RUN apk add --no-cache libc6-compat

RUN corepack enable
RUN corepack prepare pnpm@latest --activate

COPY . /usr/proxy-container
WORKDIR /usr/proxy-container

RUN npm --global install corepack@latest
RUN corepack enable
RUN corepack install

FROM base AS builder

RUN pnpm install --frozen-lockfile --ignore-scripts
Expand All @@ -21,7 +19,7 @@ FROM builder AS pruned

RUN pnpm --filter='@discordjs/proxy-container' --prod deploy pruned

FROM node:18-alpine AS proxy
FROM node:22-alpine AS proxy

WORKDIR /usr/proxy-container

Expand Down