Next.js Docker部署遇MongoDB缓冲超时及连接拒绝问题求助

将Next.js 14.2.2项目通过Docker部署到Ubuntu Linux后，网站打开时出现服务器端异常。日志显示存在MongooseError（如tags.aggregate()、questions.find()操作缓冲超时10000ms），以及MongooseServerSelectionError（连接127.0.0.1:27017被拒绝）。该项目在Vercel平台及本地使用MongoDB Atlas时可正常运行，尝试过配置MongoDB Atlas网络访问、使用MongoDB Docker镜像，但问题仍未解决。

日志内容 #

▲ Next.js 14.2.2
  - Local:        http://localhost:3001
  - Network:      http://0.0.0.0:3001

 ✓ Starting...
 ✓ Ready in 177ms
MongoDB Connected
MongoDB Connected
MongooseError: Operation `tags.aggregate()` buffering timed out after 10000ms
    at Timeout.<anonymous> (/app/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185:23)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7)
MongooseError: Operation `questions.find()` buffering timed out after 10000ms
    at Timeout.<anonymous> (/app/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185:23)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7)
...[其余日志内容]

数据库连接函数 #

export const connectDB = async () => {
  mongoose.set("strictQuery", true);

  if (!process.env.MONGODB_URL) {
    return console.log("MISSING MONGODB_URL");
  }

  if (isConnected) {
    return;
  }

  try {
    await mongoose.connect(process.env.MONGODB_URL, {
      dbName: "code-stacker",
    });
    isConnected = true;
    console.log("MongoDB Connected");
  } catch (error) {
    console.log("MongoDB Connection Failed", error);
  }
};

引发问题的函数示例 #

export async function getPopularTags() {
  try {
    await connectDB();
    const popularTags = await Tag.aggregate([
      { $project: { name: 1, numberOfQuestions: { $size: "$questions" } } },
      { $sort: { numberOfQuestions: -1 } },
      { $limit: 5 },
    ]);
    return popularTags;
  } catch (error) {
    console.log(error);
    throw error;
  }
}

Dockerfile #

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 corepack enable 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 \
  if [ -f yarn.lock ]; then yarn run build; \
  elif [ -f package-lock.json ]; then npm run build; \
  elif [ -f pnpm-lock.yaml ]; then corepack enable pnpm && pnpm run build; \
  else echo "Lockfile not found." && exit 1; \
  fi

# 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 3001

ENV PORT 3001

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/next-config-js/output
CMD HOSTNAME="0.0.0.0" node server.js

1. 确保Docker容器正确获取MongoDB环境变量 #

Docker运行时必须将MONGODB_URL传递给容器，否则会默认连接本地127.0.0.1:27017，导致连接被拒绝。运行容器时使用-e参数注入环境变量：

docker run -d -p 3001:3001 -e MONGODB_URL="your-atlas-connection-string" your-image-name

或者使用Docker Compose，在docker-compose.yml中添加环境变量配置：

services:
  app:
    build: .
    ports:
      - "3001:3001"
    environment:
      - MONGODB_URL=your-atlas-connection-string

2. 修复数据库连接函数的状态校验逻辑 #

当前isConnected变量可能存在竞态问题，导致多次调用connectDB()时误判连接状态。修改连接函数，直接使用Mongoose内置的连接状态判断：

export const connectDB = async () => {
  mongoose.set("strictQuery", true);

  if (!process.env.MONGODB_URL) {
    console.error("MISSING MONGODB_URL");
    throw new Error("MONGODB_URL is not set");
  }

  // 检查当前连接状态，如果已连接或正在连接则直接返回
  if (mongoose.connection.readyState === 1 || mongoose.connection.readyState === 2) {
    return;
  }

  try {
    await mongoose.connect(process.env.MONGODB_URL, {
      dbName: "code-stacker",
    });
    console.log("MongoDB Connected");
  } catch (error) {
    console.error("MongoDB Connection Failed", error);
    throw error; // 抛出错误，让调用方处理连接失败的情况
  }
};

3. 验证MongoDB Atlas的网络访问配置 #

• 确认Atlas控制台中已将Ubuntu服务器的公网IP加入IP白名单，或者设置为允许所有IP访问（测试用，生产环境不建议）。
• 检查Atlas连接字符串是否正确，包含用户名、密码、集群地址，且使用srv协议（如mongodb+srv://user:pass@cluster0.mongodb.net/）。

4. 优化数据库操作的错误处理 #

在调用数据库操作前，确保连接已成功建立，避免缓冲超时。修改getPopularTags函数，确保连接失败时直接抛出错误：

export async function getPopularTags() {
  try {
    await connectDB();
    // 额外验证连接状态
    if (mongoose.connection.readyState !== 1) {
      throw new Error("MongoDB connection not established");
    }
    const popularTags = await Tag.aggregate([
      { $project: { name: 1, numberOfQuestions: { $size: "$questions" } } },
      { $sort: { numberOfQuestions: -1 } },
      { $limit: 5 },
    ]);
    return popularTags;
  } catch (error) {
    console.error("Failed to get popular tags:", error);
    throw error;
  }
}

5. 如果使用本地MongoDB Docker镜像，配置网络互通 #

如果在Ubuntu上同时运行MongoDB容器，需要确保Next.js容器和MongoDB容器在同一个Docker网络中：

1. 创建自定义网络：

docker network create app-network

2. 运行MongoDB容器并加入该网络：

docker run -d --name mongodb --network app-network -e MONGO_INITDB_ROOT_USERNAME=admin -e MONGO_INITDB_ROOT_PASSWORD=password mongo

3. 运行Next.js容器时加入同一网络，并修改MONGODB_URL为容器名称（Docker会自动解析DNS）：

docker run -d -p 3001:3001 --network app-network -e MONGODB_URL="mongodb://admin:password@mongodb:27017/code-stacker?authSource=admin" your-image-name

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