为何Dockerfile 2构建的容器需加-it参数才能用Ctrl+C终止？

按照Next.js仓库指引，我成功通过docker run -p 3000:3000 nextjs-docker运行镜像，同时也编写了执行yarn start的Dockerfile 2，同样可以运行。但我发现，Dockerfile 1构建的容器可用Ctrl + C停止，而Dockerfile 2构建的容器不行，只有通过docker run -it -p 3000:3000 nextjs-docker运行时才能停止。

Dockerfile 1 #

FROM node:18-alpine AS base

# Install dependencies only when needed
FROM base 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

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
RUN \
  if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
  elif [ -f package-lock.json ]; then npm ci; \
  elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i --frozen-lockfile; \
  else echo "Lockfile not found." && exit 1; \
  fi


# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .

# 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 during the build.
# ENV NEXT_TELEMETRY_DISABLED 1

RUN yarn build

# If using npm comment out above and use below instead
# RUN npm run build

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

ENV NODE_ENV production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED 1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/public ./public

# Set the correct permission for prerender cache
RUN mkdir .next
RUN chown nextjs:nodejs .next

# 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
# set hostname to localhost
ENV HOSTNAME "0.0.0.0"

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

Dockerfile 2 #

FROM node:18-alpine AS base

# Copy files for starting app
COPY .next ./.next
COPY node_modules ./node_modules
COPY package.json ./

EXPOSE 3000
CMD ["yarn","start"] 

核心差异在于容器内PID 1进程对SIGINT信号（Ctrl+C发送的中断信号）的处理逻辑：

1. Dockerfile 1的情况
   它的CMD ["node", "server.js"]让node直接作为容器的PID 1进程运行。Node.js本身会主动处理SIGINT信号，当你在终端按下Ctrl+C时，信号会传递到容器内的PID 1进程，Node.js收到后会触发优雅退出流程，容器随之停止，不需要额外的-it参数。

2. Dockerfile 2的情况
   它的CMD ["yarn","start"]让yarn成为容器的PID 1进程。而Linux系统中，PID 1进程默认会忽略SIGINT和SIGTERM信号，除非进程主动实现了信号处理逻辑。同时：

   • 不加-it运行时，Docker没有为容器分配交互式终端（TTY），也没有将当前终端的标准输入附加到容器，导致Ctrl+C发送的SIGINT信号无法传递给容器内的yarn进程，自然无法停止容器。
   • 加上-it参数后，Docker会为容器绑定交互式终端，将当前终端的输入输出与容器关联，此时SIGINT信号能正确传递给yarn进程（或它启动的Next.js子进程），触发退出流程，容器才能停止。

替代解决方案 #

如果不想依赖-it参数，可以修改Dockerfile 2的CMD，让Node.js直接作为PID 1进程运行：

CMD ["node", "./node_modules/next/dist/bin/next", "start"]

这样就和Dockerfile 1的行为一致，无需-it即可用Ctrl+C停止容器。

内容的提问来源于stack exchange，提问作者Leech