# Dev mode not syncing changes

**URL:** <https://community.okteto.com/t/dev-mode-not-syncing-changes/587>\
**Category:** Help\
**Created:** [February 10, 2023, 9:58pm UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587 "2023-02-10T21:58:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmccorma](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/dmccorma/32/133_2.png) [@dmccorma](https://community.okteto.com/u/dmccorma)\
**Post date:** [February 10, 2023, 9:58pm UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/1 "2023-02-10T21:58:27Z")

</div>

I’m running Okteto self-hosted in EKS on AWS. I have a fairly simple application with a simple Nginx container hosting a static site. Deploying it to Okteto works fine, and the site loads correctly. Similarly, running `okteto up` to start a dev container, and then running the appropriate command within the dev container to start the web server (`/docker-entrypoint.sh nginx -g "daemon off;"`) also works correctly, and the site loads properly.

However, when I make changes to files locally, they aren’t reflected in the container, and I don’t see any log messages about files being changed.

My manifest is fairly simple:

```auto
build:
  xapiens-public-site:
    context: src
    dockerfile: Dockerfile
    args:
      DEV_ENVIRONMENT: true
      DST_TIMEZONE: America/New_York
      BASE_IMAGE_REGISTRY: ${OKTETO_BUILD_XAPIENS_PUBLIC_SITE_REGISTRY}
      BASE_IMAGE_REPOSITORY: ${OKTETO_BUILD_XAPIENS_PUBLIC_SITE_REPOSITORY}
      BASE_IMAGE_DIGEST: ${OKTETO_BUILD_XAPIENS_PUBLIC_SITE_TAG}

deploy:
  - helm dependency update "helm"
  - >-
    helm upgrade --install "xapiens-public-site" "helm"
    --set global.okteto.enabled=true
    --set global.okteto.private=true
    --set ingressRoute.enabled=false
    --set ingress.enabled=true
    --set global.environment="development"
    --set global.instance="${OKTETO_NAMESPACE}"
    --set image.registry="${OKTETO_BUILD_XAPIENS_PUBLIC_SITE_REGISTRY}"
    --set image.repository="${OKTETO_BUILD_XAPIENS_PUBLIC_SITE_REPOSITORY}"
    --set image.tag="${OKTETO_BUILD_XAPIENS_PUBLIC_SITE_TAG}"
    --set config.hostname="public-site-${OKTETO_NAMESPACE}.dev.xapiens.net"

dev:
  xapiens-public-site:
    command: ["bash"]
    sync:
      - "./src/wwwroot:/app/wwwroot"

```

My `.stignore` is very simple:

```auto
.git

```

When I log into the local Syncthing interface and open up the “recent changes” window, it DOES show the files were changed:

 ![Screenshot 2023-02-10 at 4.48.29 PM](https://us1.discourse-cdn.com/flex019/uploads/okteto/original/1X/3ca376064b80300cfac75fcead7a9081a8e59569.png)

I’m not able to log into the remote Syncthing interface – the provided username and password don’t seem to be accepted by that one.

What would my next steps be to track down the issue? Thanks!

---

<div class="post-metadata">

**Author:** ![ramiro](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/ramiro/32/6_2.png) [@ramiro](https://community.okteto.com/u/ramiro)\
**Post date:** [February 11, 2023, 12:38am UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/2 "2023-02-11T00:38:28Z")

</div>

> [@dmccorma](#):
>
> `/app/wwwroot`

Can you check that directory you “land on” when doing `okteto up` is `/app/wwwroot`? I’ve run into this issue it the past where Okteto is synchronizing to one folder, but my session is in a different folder. One way to ensure this is to set the `workingDir` property in your `okteto.yaml` to the same folder that you are synchronizing files to.

---

<div class="post-metadata">

**Author:** ![ramiro](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/ramiro/32/6_2.png) [@ramiro](https://community.okteto.com/u/ramiro)\
**Post date:** [February 11, 2023, 12:39am UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/3 "2023-02-11T00:39:33Z")

</div>

If that’s not the case, could you run `okteto doctor` from the same folder where `okteto up` is running. This will generate a diagnostics bundle. If you share it here (a link to an online drive or something like that is good), we can take a look at it.

---

<div class="post-metadata">

**Author:** ![dmccorma](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/dmccorma/32/133_2.png) [@dmccorma](https://community.okteto.com/u/dmccorma)\
**Post date:** [February 11, 2023, 1:20am UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/4 "2023-02-11T01:20:28Z")

</div>

No, when I run `okteto up` it places me at the root directory (`/`) in the dev container. However, I specified an absolute path in my sync line:

```auto
    sync:
      - "./src/wwwroot:/app/wwwroot"

```

Because of that, I would have thought the working directory wouldn’t matter.

I tried adding a `workdir` key to the `dev` section of my manifest. This did cause my dev container to come up in the `wwwroot` directory, but syncing still doesn’t occur.

The logs in the `okteto-doctor` file include some paths and hostnames on my personal machine, so I’d prefer not to post it publicly. Is there a way to provide it privately to Okteto staff, maybe?

---

<div class="post-metadata">

**Author:** ![ramiro](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/ramiro/32/6_2.png) [@ramiro](https://community.okteto.com/u/ramiro)\
**Post date:** [February 11, 2023, 1:57am UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/5 "2023-02-11T01:57:32Z")

</div>

> [@dmccorma](#):
>
> Because of that, I would have thought the working directory wouldn’t matter.

Yes, it shouldn’t matter. I just wanted to verify it to cover our bases.

> [@dmccorma](#):
>
> The logs in the `okteto-doctor` file include some paths and hostnames on my personal machine, so I’d prefer not to post it publicly. Is there a way to provide it privately to Okteto staff, maybe?

Yes. Could you share them with me via email? (is ramiro and the okteto domain)

---

<div class="post-metadata">

**Author:** ![dmccorma](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/dmccorma/32/133_2.png) [@dmccorma](https://community.okteto.com/u/dmccorma)\
**Post date:** [February 12, 2023, 3:05am UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/6 "2023-02-12T03:05:46Z")

</div>

Thanks. I sent it to you via email yesterday.

---

<div class="post-metadata">

**Author:** ![dmccorma](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/dmccorma/32/133_2.png) [@dmccorma](https://community.okteto.com/u/dmccorma)\
**Post date:** [February 14, 2023, 8:36pm UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/7 "2023-02-14T20:36:52Z")

</div>

Just wanted to post the resolution. Thanks to Okteto staff, I was able to track down the issue, and it was a problem with my Dockerfile configuration, unrelated to Okteto. I was `COPY`ing the files to Nginx’s default wwwroot directory, `/usr/share/nginx/html`, and then trying to sync a different directory, `/app/wwwroot`. D’oh. Thanks for the help, even if it ended up being my own silly mistake!

---

<div class="post-metadata">

**Author:** ![mario](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/mario/32/292_2.png) [@mario](https://community.okteto.com/u/mario)\
**Post date:** [February 16, 2023, 4:02pm UTC](https://community.okteto.com/t/dev-mode-not-syncing-changes/587/8 "2023-02-16T16:02:56Z")

</div>

Thanks for asking here to help others with the same problem!