Skip to content

Instantly share code, notes, and snippets.

@Klerith
Last active November 26, 2023 20:03
Show Gist options
  • Save Klerith/b5459b1daa4fc6d539ac373855c98039 to your computer and use it in GitHub Desktop.
Save Klerith/b5459b1daa4fc6d539ac373855c98039 to your computer and use it in GitHub Desktop.
NextJS - Dockerfile - Configuración simple y recomendada
# Fuente: https://github.com/vercel/next.js/blob/canary/examples/with-docker/README.md
# Install dependencies only when needed
FROM node:16-alpine AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn install --frozen-lockfile
# Rebuild the source code only when needed
FROM node:16-alpine AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
RUN yarn build
# Production image, copy all the files and run next
FROM node:16-alpine AS runner
WORKDIR /app
ENV NODE_ENV production
RUN addgroup -g 1001 -S nodejs
RUN adduser -S nextjs -u 1001
# You only need to copy next.config.js if you are NOT using the default configuration
# COPY --from=builder /app/next.config.js ./
COPY --from=builder /app/public ./public
COPY --from=builder /app/package.json ./package.json
# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
ENV PORT 3000
# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry.
# ENV NEXT_TELEMETRY_DISABLED 1
CMD ["node", "server.js"]
# entre 50 a 150 MB
FROM node:16-alpine
RUN mkdir -p /app
WORKDIR /app
COPY package.json /app
RUN yarn install
COPY . /app
RUN yarn build
EXPOSE 3000
CMD [ "yarn", "start" ]
# Super pesada +1GB
@Jefh15
Copy link

Jefh15 commented Apr 2, 2022

Interesante

@Jefh15
Copy link

Jefh15 commented Apr 2, 2022

Comando para generar la imagen

docker build -t nextjs-initial .

@frealpe
Copy link

frealpe commented Apr 24, 2022

=> ERROR [deps 4/5] COPY package.json npm.lock ./ tengo este problema, como lo podria solucionar

@Benji-Mtz
Copy link

Me sale un error en el RUN npm run build, a alguien le paso?

=> ERROR [7/7] RUN npm run build 2.6s ------

[7/7] RUN npm run build:
#12 1.094
#12 1.094 > build
#12 1.094 > next build
#12 1.094
#12 2.363 warn - You have enabled experimental feature(s).
#12 2.364 warn - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use them at your own risk.
#12 2.364
#12 2.383 Attention: Next.js now collects completely anonymous telemetry regarding usage.
#12 2.383 This information is used to shape Next.js' roadmap and prioritize features.#12 2.383 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
#12 2.383 https://nextjs.org/telemetry
#12 2.383
#12 2.474 info - Checking validity of types...
#12 2.492 It looks like you're trying to use TypeScript but do not have the required package(s) installed.
#12 2.492
#12 2.492 Please install @types/react by running:
#12 2.492
#12 2.492 npm install --save-dev @types/react
#12 2.492
#12 2.492 If you are not trying to use TypeScript, please remove the tsconfig.json file from your package root (and any TypeScript files in your pages directory).
#12 2.492


executor failed running [/bin/sh -c npm run build]: exit code: 1

@sebas19957
Copy link

@Benji-Mtz A mi me salió lo mismo pero cuando lo instale la primera vez y lo solucione cambiando la versión de la siguiente manera:

yarn add --dev @types/react@18.0.1 o el equivalente en npm.

@jdaniel-loyalty
Copy link

Hola saben como puedo solucionar este error?

image

@xDavid-Gabriel
Copy link

xDavid-Gabriel commented Nov 11, 2022

=> ERROR [deps 4/5] COPY package.json npm.lock ./
Para este error, borrar el yarn.lock si es que no lo estan utilizando a mi me funciono

@DiegoGutierrezP
Copy link

docker build -t nextjs-initial .
docker run --name=next-app -p 3000:3000 nextjs-initial

@julortiz
Copy link

julortiz commented Oct 8, 2023

Es importante revisar qué manejador de paquetes se está empleando, en mi caso la configuración es la siguiente para npm:

# Fuente: https://github.com/vercel/next.js/blob/canary/examples/with-docker/README.md

# Install dependencies only when needed
FROM node:16-alpine AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app
COPY package.json ./
RUN npm install --frozen-lockfile

# Rebuild the source code only when needed
FROM node:16-alpine AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
RUN npm run build

# Production image, copy all the files and run next
FROM node:16-alpine AS runner
WORKDIR /app

ENV NODE_ENV production

RUN addgroup -g 1001 -S nodejs
RUN adduser -S nextjs -u 1001

# You only need to copy next.config.js if you are NOT using the default configuration
# COPY --from=builder /app/next.config.js ./
COPY --from=builder /app/public ./public
COPY --from=builder /app/package.json ./package.json

# Automatically leverage output traces to reduce image size 
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static

USER nextjs

EXPOSE 80

ENV PORT 80

# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry.
# ENV NEXT_TELEMETRY_DISABLED 1

CMD ["node", "server.js"]

# entre 50 a 150 MB

@oscarcortez
Copy link

Nose si docker es tu fuerte, pero a ti te entiendo mejor que a otros instructores, podrias agregar mas contenido al docker course? Pdta: Eres un crack enseniando :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment