We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The included Dockerfile doesn't result in a working image.
To Reproduce
Expected behavior docker image gets built
Screenshots
=> [build-stage 2/7] RUN mkdir -p /home/node/app/node_modules && chown -R node:node /home/node/app 0.7s => [build-stage 3/7] WORKDIR /home/node/app 0.0s => [build-stage 4/7] COPY package*.json ./ 0.0s => ERROR [build-stage 5/7] RUN npm install 1.3s ------ > [build-stage 5/7] RUN npm install: #11 1.217 npm ERR! code ENOENT #11 1.221 npm ERR! syscall open #11 1.223 npm ERR! path /home/node/app/package.json #11 1.225 npm ERR! errno -2 #11 1.229 npm ERR! enoent ENOENT: no such file or directory, open '/home/node/app/package.json' #11 1.229 npm ERR! enoent This is related to npm not being able to find a file. #11 1.230 npm ERR! enoent #11 1.233 #11 1.234 npm ERR! A complete log of this run can be found in: #11 1.235 npm ERR! /home/node/.npm/_logs/2022-07-27T09_07_56_666Z-debug-0.log ------ executor failed running [/bin/sh -c npm install]: exit code: 254
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
The included Dockerfile doesn't result in a working image.
To Reproduce
Expected behavior
docker image gets built
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: