Why do not use volumes instead of copy in the docker-compose?

user_10125742 0
Viewed 563

I often make react applications as SSR. At this time, I use a docker container(docker-compose)

I write the following.(DcokerFile)

# pull base image
・
・
・
COPY package.json ./
COPY package-lock.json ./

RUN npm install

COPY . ./
CMD ["npm", "start"]

But, I suddenly thought that I can use volumes prop instead of copy prop in docker-compose. As bellow.(docker-compose.yml)

volumes:
- ./:/usr/src/app

What are pros that I use copy props instead of volumes props?

docker-compose docker reactjs
1 Answers

COPY inside your Dockerfile actually copies the files to the given path. Imagine this being carved in ice. Like once you copy everything, unless you re-build your image the files cannot be modified from outside. Where as the volume is actually creating a mounting point to the host. So if you are doing development where you need to change the code, and you use COPY you have to re-build the image everytime you want to have your changes to be in the container, whereas with volume you do not have to do rebuild your image the changes will be transfered to the container.

Use volumes during development or if you have anything you want to have a persistance, like databases and such. If you do not volume mount your database, whenever you restart your container data will be lost.

Use COPY when you are ready to ship the application and you are sure you do not modify the source code anymore.

For further reading please look at this : Docker ADD vs COPY vs VOLUME

I hope this answers your question.

user_143167610
Related