# Docker watch with Windows 10

**URL:** <https://forums.docker.com/t/docker-watch-with-windows-10/143570>\
**Category:** Compose\
**Tags:** docker-compose\
**Created:** [September 4, 2024, 10:40pm UTC](https://forums.docker.com/t/docker-watch-with-windows-10/143570 "2024-09-04T22:40:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakemackie](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/jakemackie/32/50761_2.png) [@jakemackie](https://forums.docker.com/u/jakemackie)\
**Post date:** [September 4, 2024, 10:40pm UTC](https://forums.docker.com/t/docker-watch-with-windows-10/143570/1 "2024-09-04T22:40:23Z")

</div>

I have a branch you can view [here](https://github.com/jakemackie/nextjs-template/tree/docker) that is trying to contain my Next.js application with Docker, specifically making use of the watch flag.

My issue is that i’m on Windows 10 and wonder if the file syncing works differently.

To clarify, I do see terminal output suggesting it does know when a file is edited, and so docker watch is ‘working’, my browser is just not refreshing or applying any changes thereafter. Even manually refreshing doesn’t reflect the change.

---

<div class="post-metadata">

**Author:** ![bluepuma77](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/bluepuma77/32/32688_2.png) [@bluepuma77](https://forums.docker.com/u/bluepuma77)\
**Post date:** [September 6, 2024, 6:33pm UTC](https://forums.docker.com/t/docker-watch-with-windows-10/143570/2 "2024-09-06T18:33:47Z")

</div>

I don’t get it. You update code, a new image should be build and the service restarted. Is that working or not?

---

<div class="post-metadata">

**Author:** ![rimelek](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/rimelek/32/41602_2.png) [@rimelek](https://forums.docker.com/u/rimelek)\
**Post date:** [September 6, 2024, 9:11pm UTC](https://forums.docker.com/t/docker-watch-with-windows-10/143570/3 "2024-09-06T21:11:30Z")

</div>

Does it work in an incognito Window after changing the code? If it does, it is a client side cache issue.
