feat: Implement docker deployment

[pieter-berkel]

Describe the feature you'd like to request

I would like to see how to deploy with docker, maybe in the template or at least in the documentation.

Describe the solution you'd like to see

I would like to see a docker example in the documentation.

Additional information

I already tried with the normal turborepo example but this fails because this template uses pnpm.

[juliusmarminge]

I'd be open for this - however we currently have some issues getting a normal T3 app Docker setup going so I think I'll wait until that one has been resolved before attempting to set it up for monorepos.

Follow it here: t3-oss/create-t3-app#992

[pmioduszewski]

Did someone figure it out?

[EkkoKo]

@pmioduszewski yes! I've created a PR for it right now you can go check it out
#255

Feel free to ask me questions / review it if you think there are stuff that can be written better :)

[oldo]

Thanks @EkkoKo
By taking a squiz at your PR I was able to resolve issues I was having running in docker. I was going around in circles all morning till I found your work!

[akutruff]

I did a bunch of work to dockerize this repo for fly.io. It's all here:

https://github.com/kutruff/fly-t3-turbo

(It's based on EkkOko's PR.)

[raphaelm-gioa]

What about deploying using SST ? Would that be doable even ?

[bryanjtc]

Any update on this?

[noxify]

@bryanjtc - i don't think so.

But there is a new medium articel for this topic:
https://fintlabs.medium.com/optimized-multi-stage-docker-builds-with-turborepo-and-pnpm-for-nodejs-microservices-in-a-monorepo-c686fdcf051f

Maybe it helps to get started :)

[bryanjtc]

I ended up using this Dockerfile from the official turbo docker example
https://github.com/vercel/turbo/blob/main/examples/with-docker/apps/web/Dockerfile
It works perfectly.

[Security2431]

I wanted to share with you a working Dockerfile for creating a create-t3-turbo and Next.js app.

You can find the repository on GitHub at:
https://github.com/Security2431/create-t3-turbo-with-prisma/blob/main/apps/nextjs/Dockerfile

To execute a Dockerfile, open a terminal and run the following command:

docker build -f apps/nextjs/Dockerfile -t create-t3-turbo-with-prisma:latest .

Just in case, sharing the Dockerfile content here:

ARG NODE_VERSION=20
ARG APP_DIRNAME=nextjs
ARG PROJECT=@acme/nextjs

# 1. Alpine image
FROM node:${NODE_VERSION}-alpine AS alpine
RUN apk update
RUN apk add --no-cache libc6-compat

# Setup pnpm and turbo on the alpine base
FROM alpine AS base
RUN corepack enable
# Replace <your-major-version> with the major version installed in your repository. For example:
# RUN npm install turbo@2.1.3 --global
RUN npm install turbo --global

RUN pnpm config set store-dir ~/.pnpm-store

# 2. Prune projects
FROM base AS pruner
# https://stackoverflow.com/questions/49681984/how-to-get-version-value-of-package-json-inside-of-dockerfile
# RUN export VERSION=$(npm run version)

ARG PROJECT

# Set working directory
WORKDIR /app

# It might be the path to <ROOT> turborepo
COPY . .
 
# Generate a partial monorepo with a pruned lockfile for a target workspace.
# Assuming "@acme/nextjs" is the name entered in the project's package.json: { name: "@acme/nextjs" }
RUN turbo prune --scope=${PROJECT} --docker
 
# 3. Build the project
FROM base AS builder
ARG PROJECT

# Environment to skip .env validation on build
ENV CI=true

WORKDIR /app

# Copy lockfile and package.json's of isolated subworkspace
COPY --from=pruner /app/out/pnpm-lock.yaml ./pnpm-lock.yaml
COPY --from=pruner /app/out/pnpm-workspace.yaml ./pnpm-workspace.yaml
COPY --from=pruner /app/out/json/ .

# First install the dependencies (as they change less often)
RUN --mount=type=cache,id=pnpm,target=~/.pnpm-store pnpm install --frozen-lockfile
 
# Copy source code of isolated subworkspace
COPY --from=pruner /app/out/full/ .

RUN pnpm build --filter=${PROJECT}

# 4. Final image - runner stage to run the application
FROM base AS runner
ARG APP_DIRNAME
 
# Don't run production as root
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
USER nextjs

WORKDIR /app

ENV NODE_ENV=production

COPY --from=builder --chown=nextjs:nodejs /app .
WORKDIR /app/apps/${APP_DIRNAME}

ARG PORT=3000
ENV PORT=${PORT}
EXPOSE ${PORT}

CMD ["pnpm", "start"]

[ltana6927]

I wanted to share with you a working Dockerfile for creating a create-t3-turbo and Next.js app.

You can find the repository on GitHub at: https://github.com/Security2431/create-t3-turbo-with-prisma/blob/main/apps/nextjs/Dockerfile

To execute a Dockerfile, open a terminal and run the following command:

docker build -f apps/nextjs/Dockerfile -t create-t3-turbo-with-prisma:latest .
Just in case, sharing the Dockerfile content here:

ARG NODE_VERSION=20
ARG APP_DIRNAME=nextjs
ARG PROJECT=@acme/nextjs

# 1. Alpine image
FROM node:${NODE_VERSION}-alpine AS alpine
RUN apk update
RUN apk add --no-cache libc6-compat

# Setup pnpm and turbo on the alpine base
FROM alpine AS base
RUN corepack enable
# Replace <your-major-version> with the major version installed in your repository. For example:
# RUN npm install turbo@2.1.3 --global
RUN npm install turbo --global

RUN pnpm config set store-dir ~/.pnpm-store

# 2. Prune projects
FROM base AS pruner
# https://stackoverflow.com/questions/49681984/how-to-get-version-value-of-package-json-inside-of-dockerfile
# RUN export VERSION=$(npm run version)

ARG PROJECT

# Set working directory
WORKDIR /app

# It might be the path to <ROOT> turborepo
COPY . .
 
# Generate a partial monorepo with a pruned lockfile for a target workspace.
# Assuming "@acme/nextjs" is the name entered in the project's package.json: { name: "@acme/nextjs" }
RUN turbo prune --scope=${PROJECT} --docker
 
# 3. Build the project
FROM base AS builder
ARG PROJECT

# Environment to skip .env validation on build
ENV CI=true

WORKDIR /app

# Copy lockfile and package.json's of isolated subworkspace
COPY --from=pruner /app/out/pnpm-lock.yaml ./pnpm-lock.yaml
COPY --from=pruner /app/out/pnpm-workspace.yaml ./pnpm-workspace.yaml
COPY --from=pruner /app/out/json/ .

# First install the dependencies (as they change less often)
RUN --mount=type=cache,id=pnpm,target=~/.pnpm-store pnpm install --frozen-lockfile
 
# Copy source code of isolated subworkspace
COPY --from=pruner /app/out/full/ .

RUN pnpm build --filter=${PROJECT}

# 4. Final image - runner stage to run the application
FROM base AS runner
ARG APP_DIRNAME
 
# Don't run production as root
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
USER nextjs

WORKDIR /app

ENV NODE_ENV=production

COPY --from=builder --chown=nodejs:nextjs /app .
WORKDIR /app/apps/${APP_DIRNAME}

ARG PORT=3000
ENV PORT=${PORT}
EXPOSE ${PORT}

CMD ["pnpm", "start"]

I got the error :

Attention:
Turborepo now collects completely anonymous telemetry regarding usage.
This information is used to shape the Turborepo roadmap and prioritize features.
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:
https://turbo.build/repo/docs/telemetry

• Packages in scope: @acme/nextjs
• Running build in 1 packages
• Remote caching disabled
@acme/db:build: cache miss, executing 0ce56b601eb522d1
@acme/db:build: 
@acme/db:build: > @acme/db@0.1.0 build /app/packages/db
@acme/db:build: > tsc
@acme/db:build: 
@acme/validators:build: cache miss, executing 52b1a345672e8e1c
@acme/validators:build: 
@acme/validators:build: > @acme/validators@0.1.0 build /app/packages/validators
@acme/validators:build: > tsc
@acme/validators:build: 
@acme/api:build: cache miss, executing 373d290850bf80f7
@acme/api:build: 
@acme/api:build: > @acme/api@0.1.0 build /app/packages/api
@acme/api:build: > tsc
@acme/api:build: 
Error: server probably quit: unexpected EOF
ERROR:podman_compose:Build command failed

[Security2431]

@ltana6927 Thank you for pointing it out. I'll double check it

[Security2431]

@Itsnotaka I updated the docker file above #111 (comment).

I'm not really sure, if it will fix the main cause. I noticed, prisma is no longer generated in node_modules. See the official Prisma message here https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/generating-prisma-client.

And also try to downgrade the prisma version. I'll continue research but can't promise it will go fast