One might wonder why would anyone consider Google Cloud as a hosting provider if there's Vercel?
You personally, or your organization most likely already has an infrastructure that's
capable of handling Next.js - you just need to build your app in the Docker.
Next.js and Dockerpermalink
You can use Next.js example for Docker from GitHub but here's a few hints you might find useful.
- Docker uses yarn internally, so if you're an NPM user, you need to adjust a
Dockerfilein a few places.
# Install dependencies only when needed
FROM node:14-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
COPY package.json ./
COPY package-lock.json ./
RUN npm ci
# Rebuild the source code only when needed
FROM node:14-alpine AS builder
COPY . .
COPY --from=deps /app/node_modules ./node_modules
RUN npm run build
# Production image, copy all the files and run next
FROM node:14-alpine AS runner
ENV NODE_ENV production
RUN addgroup -g 1001 -S nodejs
RUN adduser -S nextjs -u 1001
COPY --from=builder /app/next.config.js ./
COPY --from=builder /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
# 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 ["npm", "start"]
- One of the most important parts is
COPY --from=builder /app/next.config.js ./.
If you're using a custom Next.js config, remember to have this line uncommented.
Docker is running nicely on a local machine but now it is time to enter the Google Cloud domain.
Google Cloud Build and Runpermalink
First question: what is Google Cloud Build? Google says it's their CI/CD platform.
But you can utilize it to build your docker images. What we are using it for?
- Run test/lint/tsc on PR
- Build Next.js application inside docker and tell Google Cloud Run to use it
For the first one we are using following
- id: install
- id: tsc
args: ['run', 'tsc']
- id: lint
args: ['run', 'lint']
- id: test
We are using alpine version of node to match used in
For the second one we are using
- id: build
args: ['build', '--tag', 'eu.gcr.io/application:$COMMIT_SHA', '--tag', 'eu.gcr.io/application:latest', '.']
- id: push
args: ['push', 'eu.gcr.io/application:$COMMIT_SHA']
- id: push-latest
args: ['push', 'eu.gcr.io/application:latest']
- id: deploy
Steps are as follows:
- Build Docker image and tag it with current commit hash (Google Cloud Build gives us
$COMMIT_SHA) + latest tag. In this step we are also embedding
NEXT_PUBLIC_env variables as they need to be present in build time.
- Push tags
- Tell cloud run to use just the tagged Docker image with Next.js application
Note about yaml naming convention - we currently have two
cloudbuilds.yaml in repo, so it doesn't cost us much to have them in top root folder, but as a rule of thumb, if there are 3 or 4 such files e.g. one to deploy to stage and one to production, it's better to put those files inside
cloudbuild folder instead.
This blog post was about a few thoughts on how to setup Google Cloud with Next.js.
- Works almost out of the box based on Next.js example and YouTube walkthrough. You can add small adjustments like in section above.
- Google Cloud Build and Google Cloud Run also works fine - it is the fastest way of deploying images as you work in one environment that is responsible for building images and deploying them. One thing for DevOps people is to move cloud build and run configurations into something like Terraform. For this one stay tuned for next blog post.