docker-compose up -d command error in npm install step

Open
#618 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
angular, docker, docker-compose, javascript, node.js

Research direction

No repository files, tests, or entry points are identified; the report concerns the user's own Dockerfiles and docker-compose.yaml. Start by inspecting the frontend package dependencies and the Dockerfile step running npm install, then reproduce docker-compose up -d. Done means the frontend service builds without the reported Angular peer-dependency resolution error.

Written by the indexing model from the issue text.

Description

Trying to create docker image and container for my MEAN project, but error in npm install step.

Two Dockerfile created for my MEAN app, one for frontend and second for backend.
Also create docker-compose.yaml file with version and services for frontend, backend and mongo
After doing all this when I runn command "docker-compose up -d"
Building front
Step 1/8 : FROM node:16
---> 5db4e32c87c8
Step 2/8 : RUN mkdir -p /app
---> Running in 267ff76d3067
---> cf4870525fc9
Removing intermediate container 267ff76d3067
Step 3/8 : WORKDIR /app
---> 8de9146a1b9d
Removing intermediate container fe353793a0e5
Step 4/8 : COPY ./package*.json ./
---> 82b4f6a50392
Removing intermediate container ec44b06e1a7d
Step 5/8 : RUN npm install
---> Running in 0fc3770b4b87

npm notice
npm notice New major version of npm available! 8.19.3 -> 9.2.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.2.0
npm notice Run npm install -g npm@9.2.0 to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular/compiler-cli@14.2.12
npm ERR! Found: @angular/compiler@14.2.11
npm ERR! node_modules/@angular/compiler
npm ERR! @angular/compiler@"^14.1.0" from the root project
npm ERR! peer @angular/compiler@"14.2.11" from @angular/platform-browser-dynamic@14.2.11
npm ERR! node_modules/@angular/platform-browser-dynamic
npm ERR! @angular/platform-browser-dynamic@"^14.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"14.2.12" from @angular/compiler-cli@14.2.12
npm ERR! node_modules/@angular/compiler-cli
npm ERR! dev @angular/compiler-cli@"^14.1.0" from the root project
npm ERR! peer @angular/compiler-cli@"^14.0.0" from @angular-devkit/build-angular@14.2.10
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"^14.1.2" from the root project
npm ERR! 2 more (@angular/localize, @ngtools/webpack)
npm ERR!
npm ERR! Conflicting peer dependency: @angular/compiler@14.2.12
npm ERR! node_modules/@angular/compiler
npm ERR! peer @angular/compiler@"14.2.12" from @angular/compiler-cli@14.2.12
npm ERR! node_modules/@angular/compiler-cli
npm ERR! dev @angular/compiler-cli@"^14.1.0" from the root project
npm ERR! peer @angular/compiler-cli@"^14.0.0" from @angular-devkit/build-angular@14.2.10
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR! dev @angular-devkit/build-angular@"^14.1.2" from the root project
npm ERR! 2 more (@angular/localize, @ngtools/webpack)
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /root/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-12-19T17_19_19_391Z-debug-0.log
ERROR: Service 'front' failed to build: The command '/bin/sh -c npm install' returned a non-zero code: 1

Dominant language
JavaScript
Stars
1.4k
Forks
185
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from motdotla/node-lambda

All issues in motdotla/node-lambda

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.