Hey there! Let’s figure out why your Docker setup isn’t working for your Node.js + Python app on Elastic Beanstalk, and fix it up step by step.

The Core Problem with Your Current Dockerfile #

Your final image is built from node:8-alpine—this image doesn’t include a Python runtime at all! Even though you copied over your Python code and dependencies from the python:3.7 stage, there’s no Python interpreter in the Node.js image to execute those scripts, let alone access the installed packages. That’s why you’re seeing import errors when calling your Python files.

Fixes to Get Your App Running #

Here are three straightforward solutions, ordered from simplest to more complex:

1. Use a Pre-Built Image with Both Python and Node.js

The easiest approach is to start with a base image that already includes both runtimes. This avoids having to manually install either environment.

# Use an image with Python 3.7 and Node.js 8 pre-installed
FROM nikolaik/python-nodejs:python3.7-nodejs8
WORKDIR /opt/app

# Install Python dependencies first (caching friendly)
COPY requirements.txt ./
RUN pip install -r requirements.txt

# Install Node.js dependencies
COPY package.json package-lock.json* ./
RUN npm cache clean --force && npm install

# Copy the rest of your project files
COPY . ./

ENV PORT 80
EXPOSE 80

CMD [ "npm", "start" ]

2. Install Python Directly in the Node.js Alpine Image

If you prefer not to use a third-party base image, you can install Python and its dependencies directly in the node:8-alpine image. Alpine uses apk for package management, so we’ll need to install the necessary packages:

FROM node:8-alpine
WORKDIR /opt/app

# Install Python 3.7, pip, and build tools (for compiling some Python packages)
RUN apk add --no-cache python3.7 py3-pip build-base python3-dev

# Install Python dependencies
COPY requirements.txt ./
RUN pip install -r requirements.txt

# Install Node.js dependencies
COPY package.json package-lock.json* ./
RUN npm cache clean --force && npm install

# Copy project files
COPY . ./

ENV PORT 80
EXPOSE 80

CMD [ "npm", "start" ]

3. Fix Your Multi-Stage Build (Advanced)

If you want to stick with multi-stage builds, you need to ensure your final image includes both Python and Node.js environments. This requires copying the Node.js runtime into the Python image (or vice versa):

# Stage 1: Install Python dependencies
FROM python:3.7 as python-stage
WORKDIR /project
COPY requirements.txt ./
RUN pip install -r requirements.txt
COPY . ./

# Stage 2: Install Node.js dependencies
FROM node:8-alpine as node-stage
WORKDIR /opt/app
COPY package.json package-lock.json* ./
RUN npm cache clean --force && npm install
COPY . ./

# Stage 3: Combine both environments in the final image
FROM python:3.7-slim
WORKDIR /opt/app

# Copy Node.js runtime and dependencies from node-stage
COPY --from=node-stage /usr/local/bin/node /usr/local/bin/node
COPY --from=node-stage /usr/local/lib/node_modules /usr/local/lib/node_modules
COPY --from=node-stage /usr/local/bin/npm /usr/local/bin/npm
COPY --from=node-stage /opt/app ./

# Copy Python dependencies from python-stage
COPY --from=python-stage /usr/local/lib/python3.7/site-packages /usr/local/lib/python3.7/site-packages

ENV PORT 80
EXPOSE 80

CMD [ "npm", "start" ]

Elastic Beanstalk Deployment Tips #

• Test Locally First: Build and run your Docker image locally (docker build -t my-app . then docker run -p 80:80 my-app) to confirm Python scripts work before uploading to EB.
• Simplify Packaging: Just zip your Dockerfile, requirements.txt, package.json, and all project files—EB will automatically detect and build the Docker image.
• Verify Port Configuration: Ensure your Node.js app listens on the PORT environment variable (set to 80 in your Dockerfile) to match EB’s expectations.

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