npm can't find package.json when running docker container with compose

Question

I am trying to wire up my Angular 7 client app into docker compose locally.

I get the following error when I docker-compose up:

client-app    | npm ERR! errno -2
client-app    | npm ERR! syscall open
client-app    | npm ERR! enoent ENOENT: no such file or directory, open '/app/package.json'

Dockerfile:

FROM node:9.6.1

RUN mkdir -p /app
WORKDIR /app
EXPOSE 4200

ENV PATH /app/node_modules/.bin:$PATH

COPY . /app

RUN npm install --silent
RUN npm rebuild node-sass

CMD ["npm", "run", "docker-start"]

The compose part for the client is:

  client-app:
    image: ${DOCKER_REGISTRY-}client
    container_name: client-app
    ports:
      - "4200:81"
    build:
      context: .
      dockerfile: ClientApp/Dockerfile

package.json is in the ClientApp folder along-side Dockerfile, I would assume COPY . /app should copy the package.json to the container. I don't have any excludes in dockerignore. I am using Docker for Windows with Unix containers. I tried npm init before (but that will create an empty package.json anyway) and looked through the SO posts but most of the dockerfile definitions look exactly the same. I also tried: COPY package*.json ./ additionally and building the image with --no-cache.

Zeeshan Hassan Memon · Accepted Answer · 2019-06-24 20:22:58Z

18

Your Dockerfile is fine, and COPY package*.json ./ is not necessary - its being copied with your entire app.

The problem is in your docker-compose file.

you defined:

build:
      context: .
      dockerfile: ClientApp/Dockerfile

that means, your Dockerfile will accept the docker-compose context, which is 1 directory above:

├── docker-compose.yml -- this is the actual context
└── ClientApp
    ├── Dockerfile -- this is the expected context

so when the CMD is running, it is 1 directory above the package.json, therefore it cannot run the command and the container exits.

to fix it, give your docker-compose file the correct context:

build:
      context: ClientApp
      dockerfile: Dockerfile

and it should work.

edited Jun 24, 2019 at 20:22

Zeeshan Hassan Memon

8,3654 gold badges47 silver badges60 bronze badges

answered Apr 9, 2019 at 10:05

Efrat Levitan

5,6922 gold badges24 silver badges41 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

qubits Over a year ago

Thanks Efrat @Kirill Ermolov, this solved the issue, I prefer the approach with docker compose since I want to sometimes run the client separately for CI unit tests and leaving it with one working dockerfile seems a better option.

Kirill Ermolov · Accepted Answer · 2019-04-09 09:36:40Z

3

This command COPY package*.json ./ will try copy package.json from root dir. However looks like you need to copy package.json from ClientApp dir

Two way to fix this: 1) Change compose file context: ./ClientApp/ 2) Change docker file COPY ./ClientApp/package.json /app/package.json

I think better to change docker file because in feature you may want to copy some file from root dir

answered Apr 9, 2019 at 9:36

Kirill Ermolov

8107 silver badges20 bronze badges

Collectives™ on Stack Overflow

npm can't find package.json when running docker container with compose

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related