Build docker local without external reference

Hi everyone, this is my first time trying to build the project on a Docker running locally on Docker Desktop.
I noticed that links to local resources on my PC are being created in the Bind mounts section.
I'd like an image containing everything so I can distribute it for testing to a customer.

This is the target configuration.

This is the Docker Desktop screenshot.


Can you give me some suggestions?
Thanks in advance for your help.

Hi Enrico,

I don’t believe deployment of Docker, whether local or remote, offers distribution of container to external users. You can offer customers access to a local deployment via ngrok (available in Wappler) or via remote deployments (by publishing the app on a public domain).

ngrok provides a publically available url that you can share with your customer to test. However, note that the access to Docker on your system will be available until your local server is running. Once you restart Wappler, a new url with ngrok will need to be regenerated to access the web app on your local PC.

Thanks for the reply.
I'd actually like to install Docker Desktop on my client's PC and publish it to him so he can test it independently.
But I need to create an image that doesn't reference local resources on my PC.
I'm currently trying to compile Docker manually from a build in local folder.

An installation of Docker Desktop on your client’s PC and providing a Docker image is still not going to work. Each Docker deployment is reliant on the web server environment that is available to you as a developer in Wappler. So, you might end up spending time on trying to achieve an outcome that most likely is unattainable.

It’s better to either provide an access via ngrok on your local PC or deploy your app remotely for you and your client to test.

This is based on my understanding of the Docker development environment. Perhaps someone in the community has done it before and can help you if you still wish to continue trying your current approach.

the docker mounts are only made for the local development target.

If you have a live target and build for it - the full self containing image will be build.

Usually that is deployed to a remote docker server.