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.
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.
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.
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 COPYing 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!