I am trying to setup a remote docker connection (in Wappler installed on my laptop) to a server (with docker installed) that I am running in Proxmox.
The documentation uses examples from an older version of Wappler so the options and procedure does not seem to be the same or as straight forward. Can anyone point me in the right direction?
I’ve tried to generate certificates on the remote server and then copy those to my laptop, then select a .pem file but it just says waiting for ssh connection or if from from the target screen (not the manage servers screen), I enter the ip address of the virtual machine is just gives me an error and also says zsh1 command not found (Attached are some screenshots)
I have several deployments on internal (not on public providers) Docker servers. Here is my check list for this:
Make sure you have opened needed ports to access remote Docker daemon (2376 and 22) from machine where you using Wappler to target Docker server
Generate certificate to access Docker daemon. There are several nuances:
1.1 Certificates must be in your Document folder (for Windows users)
1.2 In that folder should be 3 certificate files: ca.pem cert.pem key.pem (with such exact names)
1.3 Enable TLS and set folder from 1.1
Use Test Connection button to check if this works and fix errors if needed
@Notum so do I just generate the certificates on the remote server and then copy those to my laptop? Or do I need to also generate certificates on my laptop?
So I managed to get it to work (without TLS) but for some reason the containers on my remote server (Ubuntu Desktop with Docker Desktop) does not show the container unless it’s via command line “docker ps”. So the question is…Do I need the full docker desktop or will Docker Engine be enough? I intend to use Ubuntu Server instead of Desktop version going forward hence the question.
Secondly, for some reason I also can’t generate a new docker deployment name (even after creating a brand new Wappler project). Is there a section in project settings or Wappler where I can manually maintain it? Now it’s forcing me to use the same container/deployment name or must I manually delete the container in docker first?
Example:
I am forced to use the demo_dynamic_real_estate deployment name when I was trying to get things to work but after creating a fresh project I can’t create a new one especially if I want to reuse a port of a container that was for the old project (which I deleted). So instead of just stopping the other container must I manually deleted it first?
which I should have obviously deduced from the message.
