Docker support

[geddski]

currently when running webpack dev server inside of a docker container, the changes to the source files are not picked up by webpack, so no compilation happens.

Using boot2docker vm on OSX.

[crestenstclair]

+1 having the exact same issue, would appreciate an update

Is essentially this issue:

remy/nodemon#419

[Rodeoclash]

+1

[bradbarrow]

+1

[yvann]

+1 the same for me, I can't use it.

[evandegr]

+1

[myzone]

+1

[muraken720]

+1

[joernroeder]

+1

[johnknaack]

+1

[saulshanabrook]

Use this project: https://github.com/brikis98/docker-osx-dev

It picks up file changes events

[tomchentw]

docker-osx-dev works great for me. Also its woking well with piping.

[lily-mara]

I am having the same problem, but I feel it's for a different reason. I'm using the --host 0.0.0.0 option to allow the server to listen on all interfaces, but when used in conjunction with the --hot flag, this causes problems. The hot reloader uses the provided host to create an absolute url instead of using a relative url, so all of my reloading ajax calls are going to http://0.0.0.0:8080/socket.io/ instead of just socket.io/, which would work no matter what the host/port was. I'm also proxying the server behind nginx that happens to be running on the same port, but if I wasn't, then this issue would be even worse.

[xaviervia]

+1

[vectart]

+1

[xaviervia]

@natemara about your issue, I worked around that by setting the config:

module.exports = {
  entry: {
    app: [
      "webpack-dev-server/client?:8080/",
      'webpack/hot/dev-server',
      "./src/app.coffee"
    ]
  }
}

...buuut, big disclaimer, it just fixed the socket.io address, not the livereload, which is still not working (webpack doesn't rebuild the files)

[fordlee404]

+1

[plouc]

+1

[svenhornberg]

+1

[jweidler]

+1

[ghost]

The problem has been sovled by Mark Wolfe, I have tested it in my MacBookPro.

[fordlee404]

I fixed the problem with webpack config:

watchOptions: {
    poll: true
}

@FZX thanks!

[vyorkin]

@sokra I believe it's not related to webpack-dev-server. It's just vboxfs that doesn't support fsevents or inotify.

[vyorkin]

@geddski p.s.: here is a good post about dev env with docker on OS X. My solution is to just set poll: true or if polling is too slow for you use smth like dinghy.

[langri-sha]

+1

[jimthedev]

Seems like this should probably be closed since the problem is with Virtual Box's (likely reasonable) decision to not pass through inotify events. The current relatively common fix is to use https://github.com/brikis98/docker-osx-dev

This is true for anyone using node, python, or any other language in docker who wants watchers. It really has little to do with Webpack. Perhaps it just needs to be documented, but there's little to do from a code standpoint.

[langri-sha]

@jimthedev, apparently it's not even related to just vboxsf. It is a known issue for all NFS mounts.

Here is an excerpt from the PM2 documentation:

When working with NFS devices you'll need to set usePolling: true as stated in this chokidar issue.

It seems that the best course of action is to make this information more prominent by putting it in the documentation where suitable, as you suggest.

[jimthedev]

@langri-sha, the tricky part of documenting/educating on this is that polling has implications for large project structures. It isn't always the best option. In some scenarios it might be ideal, in others, a better option might be to use docker-osx-dev to marshall the diff'ing through alternative means while leaving your webpack config untouched.

[marlonbernardes]

Thanks @fordlee404, setting watchOptions also worked for me!

watchOptions: {
    poll: true
}

[nrempel]

I believe this is an issue with docker (caused by virtual box and other virtualization tools not supporting inotify events), not webpack-dev-server.

There is a proposed solution here: moby/moby#18246

[jimthedev]

You are correct. This is an issue with Virtual Box.

[max-mykhailenko]

With new docker all works fine, My problem was in using volumes_from instead of volumes in docker-compose.yaml for node container

[enjikaka]

I'm still having issues with webpack-dev-server in docker with docker-compose and nginx-proxy.

version: '2'

services:
  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
  web-dev:
    build: .
    working_dir: /app
    volumes:
      - "./:/app"
      - /app/node_modules
    expose:
      - 9090
    environment:
      - NODE_ENV=development
      - VIRTUAL_HOST=app.dev
    command: npm run web:dev
    depends_on:
      - nginx-proxy

npm run web:dev === webpack-dev-server --config webpack/webpack.config.web.dev.js --hot --inline --watch-poll

All I get is this from nginx-proxy when trying to visit app.dev in the browser;

2016/09/14 11:04:04 [error] 33#33: 
*9 connect() failed (111: Connection refused) while connecting to upstream, 
client: 172.18.0.1, 
server: app.dev, request: "GET / HTTP/1.1", 
upstream: "http://172.18.0.4:9090/", 
host: "app.dev"

webpack-dev-server doesn't seem to allow connection or something? An express server instead of the webpack-dev-server works fine.

[SpaceK33z]

@enjikaka: you need to add --host 0.0.0.0 to your webpack-dev-server command. By default it only allows connections from localhost.

[enjikaka]

@SpaceK33z Thanks, that made it work!

[nickdima]

Quick question for people using webpack in docker for development. Isn't it slow for non trivial apps with lots of files? After all it's running inside a VM.

[langri-sha]

Yes, compared to running in your host environment, the typical setup will be slower, especially if you're using a hosted hypervisor. It's mostly impacting me on the first run and file transfers, but with proper caching these issues usually dissolve with the ease of running everything at once (development server, test runners, etc).

[enjikaka]

@nickdima We use webpack inside Docker for deving at TIDAL. (Pretty huge app) I've only tried in on my Windows machine so fat though. Works great there. :)

[bigmassa]

Not sure if this is related but I have been having a similar issue with running webpack and docker.
Scenario is on osx running webpack --watch from host to build my angular project which is linked in via a volume regularly crashes the container when it detects a file change. Similarly on ubuntu the container does not crash but the webpack --watch fails to recognise there is a change (which led me here).

I have found that increasing the number of file watchers in both os's have totally fixed my issues. For ubuntu by increasing the amount of inotify watchers https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers and for osx ive been running sudo webpack --watch.

Again this may not help but may help but thought it was a good idea to post anyway.

[evfreethy]

Anybody using RubyMine or a JetBrains IDE - please see @bartvanremortele's comment to fix this issue

[jackbraj]

I also have the same problem using laravel-mix which runs webpack.
I am using it inside docker container and my editor is phpstorm on Mac Sierra.

[Angelinsky7]

For those interested (on Window), i'm currently working on a solution inspired by another....
You can try it at https://github.com/Angelinsky7/Docker-Volume-Watcher/releases and let me know.
it uses a filewrapper and sends notification to the docker volume container

[patroza]

@Angelinsky7 you're a genius! thanks a lot!

[Angelinsky7]

@patroza :-)

[cristianfraser]

@SpaceK33z Was a Docker section added with the docs overhaul that I'm missing or not?

[magicsgxie]

In the remote server(centos7), I use command (npm run dev) to start webpack-dev-server, when I close the session, the "webpack-dev-server" is closing. How can i solve this probleam?
the dev's config like this
"dev": "webpack-dev-server --inline --progress --config build/webpack.dev.conf.js",