Wappler Version : 7.3.1
Operating System : Ubuntu 25.04
Server Model: Node JS
What do you think should happen?
The buttons to Install/update/Clean Node packages should be active on the development target.
What actually happens?
They are grayed out and not available on the local development environment.
Open a Node Project (development target). The buttons are grayed out.
Are you on the development target? And is it using Own Server for Node or docker?
I have different options there:
Hi George,
Yes to both. Development target and Node/Docker own server.
Well as the node modules are inside the docker container, docker needs to run first to be able to execute those commands.
So try starting it first.
Docker is started and running but Wappler is not recognising it as such (you can see by the exclamation mark of the status icon):
So maybe there is a different issue with identifying the status of the local deployment on Ubuntu? And this in turn causes the issue outlined in the above Bug..?
This is not urgent nor does it stop me working, installing, updating, or cleaning Node packages. Just noticed it on the new version so thought to report it.
weird that it is not detected. Maybe you can hover above the exclamation mark icon to see if an error tooltip shows.
Is it something special about the project config? Just node docker web instance and no database? Maybe you can send me the .wappler/targets/Development/docker-compose.yml to see if there is something strange in it.
And Wappler restart didn't help?
No error displayed upon hover.
No as all Docker Projects are showing the same issue (even much older Projects) so is not specific to a single Project. Nothing special in any configurations all standard deployments but am still happy to provide the files should you still wish to review them with this in mind?
Restarted Wappler and Docker Desktop several times and no difference unfortunately.
Bit stumped but will see if I can narrow it down and will report back.
Cannot connect to the Docker daemon at unix:///home/anon/.docker/desktop/docker.sock. Is the docker daemon running?
According to Gemini:
That path is not standard for Docker on Ubuntu. Normally, Docker on Linux uses:
/var/run/docker.sock
Maybe this is the issue @George?
yes that is definitely the issue for not detected running docker! What is the right path for your docker docket then?
We actually try both paths:
/var/run/docker.sock
and
~/.docker/run/docker.sock
to see where docker listens to. And both are no found on your linux installation. So is how is docker running or is it running under other user and you don't have access to docker.sock
Maybe this is the case for you:
I'm going to blame this on a recent Docker Desktop update. Oddly enough there was 4.46.0 update recently which may well have coincided with the latest Wappler release give or take (and this may have been the root issue).
I ended up adding the User back to the docker group (sudo usermod -aG docker ${USER}
), restarted Wappler, logged out and back in, and now have the features available to me that were grayed out previously, although I still have a red status icon for the actual container (which is running fine).
Cheers George!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.