I have the following project I'm trying to build an image from and docker is unable to find package.json:
root
client
server
build/
package.json
Dockerfile
Dockerfile:
FROM node:latest
WORKDIR /server
COPY ./package.json .
RUN npm install
COPY . .
EXPOSE 5000
CMD ["npm". "start"]
I have tried every directory pointer for WORKDIR and COPY that I can come up with to no success.
The left-hand side of COPY is always relative to the build context directory, usually the directory that contains the Dockerfile. You can never copy anything outside of this directory tree. If the right-hand side of COPY is a relative path, it is relative to the current WORKDIR.
In the setup you show, you are trying to copy root/package.json from the host into /server in the container.
You probably need to change the left-hand side to be relative to the root directory. The container filesystem is isolated from the host so it doesn't especially matter what the WORKDIR path actually is, just so long as it's the current directory when you run npm install or npm ci.
WORKDIR /server # or /app or anything else you'd like
COPY ./server/package*.json ./ # make sure to get package-lock.json too
RUN npm ci
Related
Is there any way to use the package installed globally instead of install the same when we run npm i.
I have the following context:
I've created a docker image with one package already installed (install statement in the Dockerfile). When I run the container with the volumen which has the javascript project and I run npm i it seems the package is installed again.
Could it be possible use the global package instead of instal it again?
If you dont want to install again during the docker build the node_modules, you can create a base image with your node_modules.
FROM node:18-alpine3.16
WORKDIR /usr/src/app
COPY package* ./
RUN npm install
docker build -t myimage .
You can tag and push it to registry (dockerhub)
Or use it locally as your new base image.
FROM myimage
WORKDIR /usr/src/app #Here are now already your node_modules
COPY . . # copy your code inside the image, or map the folder if you are in
# development
RUN npm run build # if you need a build
CMD ["mycommand","myargument"]
Note this quick, but you need to rebuild your base image if you add or update the node modules.
Consider also to use npm ci instead of npm install. In this way you keep same versions of your node modules each time you reinstall them.
Take care of security issues of the node modules as well of your base images.
run docker scan myimage, periodically to get information of your node_modules or base images need updates.
During development, it is absolutly fine to map your code folders with the docker image. While developing is not even necessary to copy your code in the image. Just map it in your WORKDIR.
After researching it seems the follow code solves my problem
WORKDIR /dir
RUN npm install package
RUN npm cache add package
RUN rm -rf *
WORKDIR /
I'm building Express using Docker.
Previously, I uploaded it to the Ubuntu server using the Dockerfile.
But suddenly there was an error.
When building Docker Image, there was an error that could not read the file.
When I build with Docker and run, It can't find the javascript module I made.
An error occurred even if dockerfile2 was used instead of dockerfile1.
I don't know what the problem is.
I updated Docker, too.
Docker version 20.10.8,
Error Msg.
(when use dockerfile1)
Error msg : Cannot find module
Error Msg.
(when use dockerfile2)
> socket_example#1.0.0 start /usr/src/app
> node app.js
internal/modules/cjs/loader.js:905
throw err;
^
Error: Cannot find module './AgoraApi'
Require stack:
- /usr/src/app/src/audioChat/audioChannelHandler.js
- /usr/src/app/src/multiplay/rooms/GameRoom.js
- /usr/src/app/app.js
docker file1
FROM node:14
WORKDIR /
COPY package.json ./
RUN npm install
COPY ./ ./
EXPOSE 4000
CMD [ "npm", "start" ]
docker file2
FROM node:14
WORKDIR /usr/src/app
COPY package.json /usr/src/app
RUN npm install
COPY . /usr/src/app
EXPOSE 4000
CMD [ "npm", "start" ]
dockerignore file
.git
.gitignore
README.md
webpack.config.js
NAF-Gallery-Test.git
package-lock.json
backup
logs
node_modules
config/sql/*
!src
!util
Folder Structure
app.js
config.js
src
ㄴaudioChat
ㄴagoraApi.js
util
ㄴvipRoomManager.js
...
I am trying to deploy my nuxt project with docker so i create Dockerfile and docker-compose.yml and also the .dockerignore file but it giving me errors it's my first time to work with docker i follow the process from the official documentation but i do not really a strong understanding about docker. If i miss something or anymore understand why there is an error while i'm trying to build docker-compose please let me know.
Dockerfile
FROM node:14.15.4-alpine
#create destination directory
RUN mkdir -p /twin_login/app
WORKDIR /app
COPY package*.json ./app
#update and install dependency
RUN apk update && apk upgrade
RUN apk add git
RUN apk add python3
#copy the app, note .dockerignore
COPY . .
COPY . /app
RUN npm install
#build necessary, even if no static files are needed,
RUN node -v
RUN npm -v
#set app serving to permissive / assigned
ENV HOST 0.0.0.0
#expose 8000 on container
EXPOSE 8000
CMD ["npm", "start"]
Docker-compose.yml
version: '3'
services:
web:
build: .
ports:
- 8000:3000
volumes:
- ./twin_login:/app
stdin_open: true
tty: true
networks:
- twin_login
networks:
twin_login:
external: true
.dockerignore
node_modules
.gitignore
.nuxt
Error this is the error i am getting
WARN[0000] Found orphan containers ([twin_management_screen_nuxt_1 twin_management_screen_nuxt_run_2d8fca86d2ca twin_management_screen_nuxt_run_6d5ee3c9b0ba twin_management_screen_nuxt_run_881e46ae1ad1 twin_management_screen_nuxt_run_5089871620b5]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
The error you found is not an error, just a warning (thus WARN[0000]) that you have orphaned containers that you should clean up with --remove-orphans (because they take up a lot of space on your system).
Check the syntax of your yml file and possibly also the Dockerfile, indentation is strict.
It can look as though you forgot the "run" part of your start CMD.
A tip is to do as little as possible in the Dockerfile and most of the stuff in docker-compose. This is the minimum stuff you need in your Dockerfile:
FROM node:xxx.xxx
ENV NODE_ENV=dev
WORKDIR /
COPY ./package*.json ./
RUN npm install
COPY . .
EXPOSE 8080 #or other
CMD ["npm", "run", "start"]
Unable to Copy config file in my project dir to /etc/nginx/conf.d/default.conf
source file location:
/app/nginix.conf
COPY nginx.conf /etc/nginx/conf.d/default.conf
destination : /etc/nginx/conf.d/default.conf
Steps in docker file :
Tried the multi stage build:
- FROM node:8.9.0 as buid
- WORKDIR /app
- COPY package.json package-lock.json ./
- RUN npm install
- COPY . ./
- RUN npm run build
- FROM nginx:alpine
- RUN mkdir -p /var/www/html/client
- COPY --from=buid /app/nginix.conf /etc/nginx/conf.d/default.conf
- COPY --from=buid /app/build/ /var/www/html/client
Tried commenting the first copy command, and it was able to copy the build and it was good.
when it is able to find the build in the app dir why is it not able to find the nginix.conf file which is also in the same dir, did a ls -la and saw the nginix.conf file.
TIA
If the source file path is /app/nginix.conf then dockefile should contain:
COPY /app/nginx.conf /etc/nginx/conf.d/default.conf
If you're running docker build command from /app directory on your host then your above dockerfile should work.
Update:
If you're expecting /app/nginx.conf file of node docker image to present in nginx:alpine image then you need to use multi-stage docker builds.
Change your dockerfile to
FROM node as build
WORKDIR /app
COPY package json files
RUN npm build
FROM nginx:alpine
COPY --from=build /app/nginx.conf /etc/nginx/conf.d/default.conf
This will copy /app/nginx.conf file from node image to nginx:alpine image.
If somebody is still struggling with this....
changing the WORKDIR from app to builddir worked!
FROM node:alpine as builder
WORKDIR '/builddir'
COPY package.json .
RUN npm install
COPY . .
RUN npm run build
FROM nginx:alpine
COPY --from=builder /builddir/build /usr/share/nginx/html
RUN rm /etc/nginx/conf.d/default.conf
COPY nginx/nginx.conf /etc/nginx/conf.d
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]
I've been trying for some time to cache node_modules on a Docker build. I've tried several approaches including the one here, but without success.
My main reason to cache is because it takes 30+ minutes to build my image, which is way too much.
My Dockerfile:
# This image will be based on the oficial nodejs docker image
FROM node:4.2.1
RUN npm install -g jspm#0.17.0-beta.7 && \
npm install -g gulp && \
npm install -g tsd
# Use changes to package.json to force Docker not to use the cache
# when we change our application's nodejs dependencies:
ADD package.json /src/package.json
RUN cd /src && npm install
# Put all our code inside that directory that lives in the container
ADD . /src
# Set in what directory commands will run
WORKDIR /src
# Install dependencies
RUN cd /src && \
tsd reinstall -so && \
jspm install && \
gulp build -p
# Tell Docker we are going to use this port
EXPOSE 3000
# The command to run our app when the container is run
CMD ["npm", "run", "start-production"]
I do not have a .dockerignore file. I added one before but it still didn't cache my node_modules.
So, how to I cache my node_modules? Feel free to suggest modifications to the Dockerfile.
Thanks!
I'm not sure whether it is the root of the error, but try to specify the destination folder in the ADD command and not the destination file.
ADD package.json /src
Moreover, you can use COPY instead of ADD (ADD can work with url and archives but you don't need it here).
You can also specify your working directory earlier in the file.
Try with this code :
# This image will be based on the official nodejs docker image
FROM node:4.2.1
RUN npm install -g jspm#0.17.0-beta.7 && \
npm install -g gulp && \
npm install -g tsd
# Set in what directory commands will run
WORKDIR /src
# Use changes to package.json to force Docker not to use the cache
# when we change our application’s nodejs dependencies:
COPY package.json ./
RUN npm install
# Put all our code inside that directory that lives in the container
COPY . ./
# Install dependencies
RUN tsd reinstall -so && \
jspm install && \
gulp build -p
# Tell Docker we are going to use this port
EXPOSE 3000
# The command to run our app when the container is run
CMD ["npm", "run", "start-production"]