[bug] Implement Multi-Stage Build in Dockerfile

[Saurav-Pant]

Describe the bug

The current Dockerfile lacks a multi-stage build. Adding this enhancement significantly reduces the image size, optimizes distribution, and simplifies container management.

To Reproduce

Go to Dockerfile
and add this
COPY package*.json ./ before this line COPY . .

Expected Behavior

No response

Screenshot/ Video

No response

Additional context

No response

[github-actions]

Hey Hey! 👋🏻 Thank you so much for raising an issue. The maintainers will get back to you soon for discussion over the issue! In the meantime join our Discord server and checkout our YouTube channel.

[SaptarshiSarkar12]

@AnuragThePathak Can I work on this issue?

[AnuragThePathak]

@SaptarshiSarkar12 go ahead

[SaptarshiSarkar12]

@AnuragThePathak Thank you for assigning this issue to me 😁

[SaptarshiSarkar12]

@AnuragThePathak I have tried multiple approaches to add muti-stage docker build. But, craco start is not working without node_modules thereby increasing the size of the image. Please let me know how I should solve this problem.

My Dockerfile 👇

FROM node:17-alpine AS deps
COPY package.json ./
RUN npm install

FROM deps AS builder
COPY . .
RUN npm run build

FROM node:17-alpine AS runner
COPY --from=builder build ./build
RUN npm install -g serve
EXPOSE 3000
CMD ["serve", "-s", "build"]

The error 👇

> start
> craco start

sh: 1: craco: not found

[AnuragThePathak]

@SaptarshiSarkar12 you should use package*.json then only package-lock.json will be copied

[SaptarshiSarkar12]

@AnuragThePathak I was using npm install previously. So, if I use package-lock.json, then, I also need to change the command to npm ci, right?

[AnuragThePathak]

Yes you must use npm ci else we may see unintended behaviors in production.

[SaptarshiSarkar12]

@AnuragThePathak Okay. I have added. Please check #827