Closed HsuTing closed 6 years ago
@HsuTing I need the debug output. What is the base image are you trying to run this on?
@rizowski I added the debug output in description.
I do not know OS. I just use node:latest
in docker
. I saw the Dockerfile of node:latest
, and I think OS is debian:jessie
.
What is the steps to reproduce this? Are you editing files from a volume or inside the container directly?
I am just editing one file inside the container directly.
Oh, I use docker
in win 10
. Do this impact the watch
?
Technically it shouldn't matter that docker is on windows. Because you are running everything inside the container and not using a volume. So it should be isolated.
I know. I just want to give more detail to you.
This is what I am using to test the problem. I copied over the files from tests/integration/test-files
and modify one of these files to try to trigger the file changed event. I wasn't able to get it to fire.
FROM node:latest
ENV DEBUG="esw:*"
RUN mkdir /var/app
WORKDIR /var/app
RUN apt-get update
RUN apt-get install -y vim
RUN npm i -g eslint-watch eslint
COPY test .
COPY package.json .
RUN npm i
CMD esw ./ --cache --ext .js -w --color
I use another way to test.
docker run -it node:latest /bin/bash
git clone <eslint-watch repo>
apt update
and apt install -y vim
npm i -g eslint eslint-watch
tests
and package.json
to new folder, and run npm i
in new folder.esw ./ --cache --ext .js -w --color
CMD
and run docker exec -it <container id> bash
.tests
.This does not work again. Is exec
to make this bug?
Environment
Basic Description of the problem
Does not watch when using in
node
image ofdocker
.How to reproduce it
esw ./ --cache --ext .js -w --color
Debug output: