React+Node.js应用Docker化问题：容器已退出无端口显示

Hey there! Let's work through why your Docker containers are exiting immediately and not showing up in docker ps. Here's a step-by-step breakdown to get things running smoothly:

1. First, Check Container Logs (This is Critical!) #

The fastest way to figure out why your container crashed is to look at its runtime logs. Grab one of your container IDs (like 123 from your output) and run:

docker logs 123

This will spit out all the output the container generated when it tried to start—you’ll almost certainly find clues here: missing dependencies, incorrect file paths for server.js, runtime errors in your Node code, or even port conflicts.

2. Verify Your Dockerfile Setup #

Since you followed the Node.js Docker guide, double-check these common pitfalls in your Dockerfile:

• Working Directory & File Paths: Make sure you’re setting a clear working directory and copying files correctly. A standard setup looks like this:

  FROM node:18-alpine
  WORKDIR /app
  # Copy package files first to leverage Docker's cache
  COPY package*.json ./
  RUN npm install
  # Copy the rest of your application code
  COPY . .
  # Declare the port your Node app listens on
  EXPOSE 3000
  # Start the app (ensure server.js lives in /app!)
  CMD ["node", "server.js"]
  

  If your server.js is in a subfolder (like ./src/server.js), adjust the CMD path accordingly.
• React vs. Node Confusion: If this is a full-stack app, confirm your server.js is properly serving the React build (if you’re using a production setup). For a React dev server in Docker, you’ll need to add flags like --host 0.0.0.0 to allow external access to the container.

3. Make Sure You’re Mapping Ports Correctly #

The missing port info in docker ps -a is almost certainly because you didn’t map the container’s port to your host machine when starting the container. Use this command to run your image:

docker run -p 3000:3000 mruanova/app

The -p host-port:container-port flag creates the necessary port mapping—without it, Docker won’t expose the port to your local machine, so you’ll never see it in the PORTS column.

4. Test Your App Locally First #

Before diving deeper into Docker, confirm your app works without containers:

npm install
node server.js

If this fails locally, fix those issues first—Docker can’t resolve problems with your Node app itself.

5. Check the Container Exit Code #

You can get extra context from the exit code using:

docker inspect 123 | grep ExitCode

• Exit code 0: The app ran successfully but exited (common if your script is a one-time task instead of a long-running server).
• Exit code 1: A general application error (go back to the logs for details!).
• Exit code 137: The container was killed due to out-of-memory issues (try increasing Docker’s allocated memory in settings).

Start with the logs—they’ll point you straight to the problem. Let me know what you find if you need more help!

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