Vite + Vue app file watch, rebuild not works on docker container

[BeycanDeveloper]

Describe the bug

there is a { usePolling: true } option in the Vite documentation. If I activate this, yes filewatch works.

However, this time the container cannot be closed at all and docker crashes.

Can anyone help with this?

Here are the relevant codes below

Compose

version: '3.8'

services:
  node:
    build:
      context: .
    container_name: app-js
    ports:
      - "3035:3000"
    volumes:
      - ./:/usr/src/app
    init: true

Dockerfile

FROM node:lts-alpine

WORKDIR /usr/src/app

COPY package.json .

RUN npm cache clean --force
RUN npm install

COPY . .

EXPOSE 3000

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

vite.config.js

import { fileURLToPath, URL } from 'node:url'

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'

// https://vitejs.dev/config/
export default defineConfig({
    plugins: [
        vue(),
    ],
    build: {
        assetsDir: '.',
        assetsInlineLimit: 0,
        assetsInclude: ['**/*'], 
        rollupOptions: {
            input: {
                main: 'src/main.js',
            },
            output: {
                entryFileNames: 'main.js',
                chunkFileNames: '[name].js',
                assetFileNames: '[name].[ext]', 
            },
        },
    },
    resolve: {
        alias: {
            '@': fileURLToPath(new URL('./src', import.meta.url))
        }
    },
    server: {
        port: 3000,
        host: true,
        strictPort: true,
    }
})

In addition, I have examined and searched for many things along with the issue below, but I could not find any results. The only solution right now seems to be usePolling, but when you use it, the container can never be closed and docker crashes.

#4116

Reproduction

https://stackblitz.com/edit/vitejs-vite-rfzxm6?file=docker-compose.yaml,package.json,vite.config.js&terminal=dev

Steps to reproduce

npm run dev

System Info

2024-01-03 10:37:37 my-app  |     OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
2024-01-03 10:37:37 my-app  |     CPU: (12) x64 AMD Ryzen 5 4600H with Radeon Graphics
2024-01-03 10:37:37 my-app  |     Memory: 5.12 GB / 7.45 GB
2024-01-03 10:37:37 my-app  |     Container: Yes
2024-01-03 10:37:37 my-app  |     Shell: 5.2.15 - /bin/bash
2024-01-03 10:37:37 my-app  |   Binaries:
2024-01-03 10:37:37 my-app  |     Node: 20.10.0 - /usr/local/bin/node
2024-01-03 10:37:37 my-app  |     Yarn: 1.22.19 - /usr/local/bin/yarn
2024-01-03 10:37:37 my-app  |     npm: 10.2.3 - /usr/local/bin/npm
2024-01-03 10:37:37 my-app  |   npmPackages:
2024-01-03 10:37:37 my-app  |     @vitejs/plugin-vue: ^4.5.2 => 4.5.2 
2024-01-03 10:37:37 my-app  |     vite: ^5.0.10 => 5.0.10

Used Package Manager

npm

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-rfzxm6 (Open reproduction)

[sapphi-red]

Looking at #15492 (comment), I guess you're using docker on Windows.
This is a limitation of WSL2: https://vitejs.dev/config/server-options.html#server-watch:~:text=Using%20Vite%20on,CPU%20utilization