services:
nest:
build:
context: .
dockerfile: Dockerfile
target: ${DOCKER_TARGET:-dev} # Defaults to "dev" if not specified
container_name: nestjs_api
env_file:
- .env.${DOCKER_TARGET:-dev} # Dynamically load .env.dev or .env.p
environment:
NODE_ENV: ${NODE_ENV}
DATABASE_HOST: ${DATABASE_HOST}
DATABASE_PORT: 5432
DATABASE_USER: ${DATABASE_USER}
DATABASE_PASSWORD: ${DATABASE_PASSWORD}
DATABASE_NAME: yt-watch
REDIS_HOST: redis
REDIS_PORT: 6379
ports:
- "3000:3000"
volumes:
- .:/app
- /app/node_modules
command: npm run start:dev
depends_on:
- postgres
- redis
networks:
- backend
profiles: ["dev", "prod"]
develop:
watch:
- action: sync+restart
path: .
target: /app
ignore:
- node_modules/
postgres:
image: postgres:17
env_file:
- .env.${DOCKER_TARGET:-dev}
restart: always
environment:
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
POSTGRES_DB: yt-watch
ports:
- "5432:5432"
volumes:
- yt-watch-data:/var/lib/postgresql/data
networks:
- backend
redis:
image: redis:8.2
env_file:
- .env.${DOCKER_TARGET:-dev}
ports:
- "6379:6379"
volumes:
- redis-data:/data
networks:
- backend
volumes:
yt-watch-data:
redis-data:
networks:
backend:
driver: bridge
#docker image not able to build
4 messages · Page 1 of 1 (latest)
Dockerfile
# ----------------------
# Base image for both dev & prod
# ----------------------
FROM node:24.5.0-alpine AS base
WORKDIR /app
COPY package*.json ./
RUN npm ci
# ----------------------
# Development stage
# ----------------------
FROM base AS dev
COPY . .
CMD ["npm", "run", "start:dev"]
# ----------------------
# Build stage (for prod)
# ----------------------
FROM base AS build
COPY . .
RUN npm run build
# ----------------------
# Production stage
# ----------------------
FROM node:24.5.0-alpine AS prod
WORKDIR /app
COPY --from=build /app/package*.json ./
COPY --from=build /app/node_modules ./node_modules
COPY --from=build /app/dist ./dist
CMD ["node", "dist/main.js"]
So what is happening?
the image of my backend is not generationg