Isn't this COPY . . only going to copy the source once, when you build up the container?
https://github.com/ArtoszBart/next-issue/blob/2e6ac6b3f252f172327d0ec22d205ad46ce1df63/Dockerfile.dev#L6

I'm pretty sure that if you want "outside" changes to be reflected inside the container in real time (without rebuilding), you need to mount the directory as a volume instead of just copying it.

Isn't this COPY . . only going to copy the source once, when you start up the container? https://github.com/ArtoszBart/next-issue/blob/2e6ac6b3f252f172327d0ec22d205ad46ce1df63/Dockerfile.dev#L6

I'm pretty sure that if you want "outside" changes to be reflected inside the container in real time (without restarting compose), you need to mount the directory as a volume instead of just copying.

Exactly. Volume mapping is in the docker-compose.yml file.

As I said earlier:

After saving changes in page.tsx on the PC, the .next/server/chunks/ssr on PC is updated same as page.tsx in container

Same problem here in nextjs 15 doesnt work wit turbopack in nextjs 14.2.5 its work

nvm after I mirrored this one it works somehow: volumes:

- ./:/app
- ./apps/web/node_modules:/app/apps/web/node_modules
- ./apps/web/.next:/app/apps/web/.next

Downgraded to [email protected]:

With:

    volumes:
      - ./:/app

After saving changes in page.tsx on the PC, the .next/server/app/page.js both on PC and container is updated same as page.tsx in container. However changes in app running inside container remains not updated in browser. After page reload i have:

Server Error

Error: Could not find the module "/app/node_modules/next/dist/client/components/app-router.js#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

The same error occurs with:

    volumes:
      - ./:/app
      - ./node_modules:/app/node_modules
      - ./.next:/app/.next

Having same issue with "next": "^15.0.0".
Adding volume change is updated in docker but log never compile the new update.

Placing

const nextConfig: NextConfig = {
  output: "standalone",
  outputFileTracingRoot: path.join(__dirname, "../../"),
  // eslint-disable-next-line @typescript-eslint/no-explicit-any
  webpackDevMiddleware: (config: any) => {
    config.watchOptions = {
      poll: 1000,
      aggregateTimeout: 300,
    };
    return config;
  },
};

Inside the next.config.ts worked for me. You will get warnings in the console when you start the container:

⚠ Invalid next.config.ts options detected:
frontend-1          |  ⚠     Unrecognized key(s) in object: 'webpackDevMiddleware'
frontend-1          |  ⚠ See more info here: https://nextjs.org/docs/messages/invalid-next-config

Keep in mind that you still need to add volumes in your docker-compose.yml file:

frontend:
    build:
      context: .
      dockerfile: ./apps/frontend/Dockerfile
    ports:
      - "3000:3000"
    volumes:
      - ./apps/frontend:/app/apps/frontend
    environment:
      - NODE_ENV=development
    depends_on:
      - backend

It's still not working for me

It's still not working for me

This worked for me:

Edit the file "package.json" like so:

"scripts": {
"dev": "WATCHPACK_POLLING=true next dev",
...
}

This worked for me:

frontend\next.config.ts

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  output: "standalone",
};

export default nextConfig;

docker-compose.dev.yaml

...
  frontend:
    build:
      context: ./frontend
      dockerfile: Dockerfile
      target: dev
    container_name: frontend-dev
    volumes:
      - ./frontend:/app
      - /app/node_modules
    restart: unless-stopped
    ports:
      - "3000:3000"
    env_file:
      - .env
    depends_on:
      - backend
    networks:
      - devnet
    command: npm run dev
...

frontend\package.json

  "scripts": {
   "dev": "WATCHPACK_POLLING=true next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
"dependencies": {
        "lucide-react": "^0.479.0",
        "next": "^15.2.4",
        "next-themes": "^0.4.6",
        "react": "^19.1.0",
        "react-dom": "^19.1.0",
        "react-hook-form": "^7.55.0",

  },

Another approach to accomplish this is by utilizing Docker compose watch feature. Here is example:

services:
  web:
    build: 
      dockerfile: dev.Dockerfile
    develop:
      watch:
        - action: sync
          path: .
          target: /app
          ignore:
            - node_modules/