Vite server on docker build keeps restarting

[faridguzman-ict]

Describe the bug

My current docker file is as follows:

FROM node:20-slim AS base

ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"


COPY package.json .
RUN corepack enable

RUN pnpm install
RUN pnpm update

RUN mkdir node_modules/.cache && chmod -R 777 node_modules/.cache

COPY . .

EXPOSE 5173

CMD ["pnpm", "run", "dev"]

when i build in in docker, it runs with pnpm run dev, but seems to detect changes in the vite.config.ts file and restarts every second

i used pnpm for the build, is their anything wrong in the dockerfile script?

it seems to run fine with npm though

Reproduction

https://stackblitz.com/edit/vitejs-vite-ajmfgr?file=vite.config.ts

Steps to reproduce

Install docker and docker engine

sudo apt-get update

sudo apt-get install apt-transport-https ca-certificates curl gnupg lsb-release

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update

sudo apt-get install docker-ce docker-ce-cli containerd.io

then run docker compose

docker compose up -d --build

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 3.62 GB / 31.69 GB
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.6.12 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (117.0.2045.43)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-vue: ^4.3.4 => 4.3.4
    @vitejs/plugin-vue-jsx: ^3.0.2 => 3.0.2
    vite: ^4.4.9 => 4.4.9

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[stackblitz[bot]]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-ajmfgr (Open reproduction)

[bluwy]

The filesystem watcher is reporting that tsconfig.json and vite.config.ts, so Vite is reacting to that by restarting the server. I'm not sure what's causing it by it seems like something external is constantly "touching" the file. In any case, you can workaround it by setting server.watcher.ignored: ['./vite.config.ts']

[faridguzman-ict]

Unfortunately this didn't solve the problem as it keeps restarting until the js heap runs out of memory, i will use npm until its resolved.

[josu-dev]

I encountered the same bug that the server keeps restarting, i tried to ignore the vite.config.js in my case, but ignoring with relative path didn't work for me, so i used a the glob "*/**/vite.config.js".

With the glob the restarts stopped but now the server didn't answer any of my request from outside and inside the container. How @jd-apprentice the unique solution that we could reach was to set a workdir in the dockerfile, that gets the app running with or without ignoring the vite.config.js

[paulhaem]

Facing the same issue using npm. In addition to vite.config.js .env.local and env.sample are also triggering a server restart. Any news regarding this?

[jd-apprentice]

Had the same issue and the solution was to add a workdir

WORKDIR /app

@J-Josu and I are trying to understand what is happening there

[jd-apprentice]

@bluwy Do you have an idea why this works like this?

[bluwy]

I'm not sure. If the project is in the root directory, I've heard that it generally causes issues though, and this is probably one of those.

[lequoctrung-it]

Is there any answer for that. My project structure is /. when i add workdir like /app. it is not found the files

[mikesamm]

This worked for me, thank you.

[chanyoung1998]

i solved this issue using docker volume. mapping working directory to docker volume

FROM node

WORKDIR /home

COPY . /home

RUN npm install

EXPOSE 5173

CMD ["npm", "run", "dev"]

services:
  my_sevice:
    image: my_image
    volumes:
      - my-volume:/home
    ports:
      - "11221:5173"
volumes:
  my-volume: