Docker Desktop + NodeJS + Google Drive

Wappler Version : 3.5.1
Operating System : WIN10PRO

Expected behavior

The project’s app to be available on localhost:8100 and the Docker web container to be running.

Actual behavior

localhost:8100 can not be loaded and the Docker web container is restarting continuously until exited. The db container does keep running btw.

How to reproduce

  1. Setup a NodeJS project with file folder on shared/cloud drive (Google Drive in my case)
  2. Setup local Docker target and remote Docker target
  3. Test deploying the app on remote Docker target >> That works fine and app is shown on remote target.
  4. Test deploying the app on the local Docker target >> That returns a success message saying the build was successful and all services are launched. However, in Docker Desktop can be seen the web container is restarted all the time and finally stops. It shows the following error in the logs: [nodemon] Internal watch failed: ENOSYS: function not implemented, scandir '/opt/node_app/views'. As a result the app is not accessible on localhost through the browser.

I am really sure this only happens when the project is on a cloud drive. Tested several times with the exact same project in local and cloud folders. Always works fine on local, never works in cloud folders.

Please let me know if you need more information.

You probably need to update your nodejs project and install the latest node modules. Try running the “Install Node Packages” from the bottom toolbar:

image

Thanks for the quick replay @George!

Tried that, but get this message then because the Docker container is not running:

image

I see well seems you have problems with your docker container, try redeploying and check the logs for errors.

What are you using google drive for?

I have to say that’s a valid question :grimacing:

First of all because we store all our company data in the cloud, but that’s a rule I can break of course.

Besides that weak first argument I like to save the project files on cloud hosting to be able to work on an up-to-date version of the same project on a different device, even if it wasn’t pushed to Github on the device that was used for working on it previously.
Pushing changes to Github at the end of a work cycle would be a solution for that, I know :blush:

Oh ok. But you are actually not trying to run a server on top of google drive files right?

Not for remote targets. However it’s the project folder storage location, so it is used by Docker Desktop as the file source for the (local) Docker target.

1 Like