Wappler not see docker on Ubuntu or OFFLINE or Not Running

jndaniels0 · December 19, 2024, 4:39am

Hi y'all,
I loaded Ubuntu 24.x LTS - and was pretty excited with I got everything loaded. But my excitement turned into sad-day fast.

Maybe somebody ran into this too?

Wappler says
Server: Docker Desktop is not runnng! OORRRR it might say offline (red).
If i hit deploy - it builds the container then says the not running

I've followed docker.com install for ubuntu page down to the T . Even uninstalled it and RE-Installed it.No luck. I did the systemctl command to start it. Nothing keeps it going. Im out of ideas.

This other error comes up as well
getting image info for undefined: connect EACCESS - appears in the lower right corner for about 6 seconds. Mentions that the docker.sock is in /var/run/docker - and it exists.

R4v3n · December 19, 2024, 8:26am

I have the exact same problem on Linux Mint 22 (which is based on Ubuntu 24) and I don't even know what is going on. It's annoying me really hard.
It must have something to do with the new Ubuntu version and I don't know what this may be.

R4v3n · December 19, 2024, 8:46am

Everytime I try to set the target for the local docker environment and when I press test connection. Everything appears to work.
When I press a second time onto it, the following happens:

Apple · December 19, 2024, 9:41am

If you don't care about Docker Desktop you can uninstall it and install the Docker provided by the maintainers of your Linux distro, the package is docker.io

apt-get update
apt-get install docker.io

George · December 19, 2024, 9:45am

Also make sure the docker socket is accessible by the current user, having the right permissions

R4v3n · December 19, 2024, 10:04am

I already did change the permissions for this file and it doesn't change a thing sadly.

R4v3n · December 19, 2024, 10:11am

I can stop the docker containers by pressing two times on the "play" button.
But I cannot start them afterwards through Wappler itself.

But I cannot start them at all through wappler, though there is a positive connection when I test it:

George · December 19, 2024, 10:21am

try restarting Wappler.

Normally containers are auto started when you open the Wappler project. You don't need to stop them

R4v3n · December 19, 2024, 10:28am

This won't solve the issue at all.
A restart can't help here, when Wappler itself only recognizes a connection while pressing "test connection". Otherwise it does not recognize a connection.

George · December 19, 2024, 10:38am

try running some commands from the terminal like:

docker ps

docker -v

ls -la /var/run/docker.sock

George · December 19, 2024, 10:48am

Also make sure you have installed as per docker docs:

Install docker service:
Install using the apt repository
Optionally install Docker Desktop
Install Docker Desktop on Ubuntu
add your current user to the docker group afterwards by executing in the terminal:
sudo usermod -aG docker $USER
newgrp docker

R4v3n · December 19, 2024, 11:37am

Apparently I did wrong research, while trying to give out the permissions for /var/run/docker, the connection was still not able to be established.
For me the docker.sock is NOT INSIDE /var/run/docker.
There is a difference between /var/run/docker = a folder
and between /var/run/docker.sock = a .sock file.
George you were right, I just did not watch out enough for the right type of the file apparently.
(Thank you very much, you saved the day [maybe even the year] for me; along with the error logs from Wappler which appeared after reinstalling the whole docker engine following this guide: Ubuntu | Docker Docs and this guide: Ubuntu | Docker Docs)

@jndaniels0
Make sure that your docker.sock is really in the /var/run/docker folder or rather just in the /var/run directory.
This is where you have to change the permissions so Wappler will be able to start docker itself.

George · December 19, 2024, 11:52am

No docker.sock is really directly under /var/run

R4v3n · December 19, 2024, 1:16pm

Yep!

jndaniels0 · December 19, 2024, 2:47pm

Hi @George
All of that exists including the socket ALTHOUGH, i think i forgot to add myself to the docker group. I will run thru these items once again.

@R4v3n
Looks like we are having the EXACT same issue. Please if you find a fix before i do , please share

To everybody,
Thank you again as usual!

Cheese · December 19, 2024, 3:13pm

FOR UBUNTU!!

Do you not see Docker Desktop in your Applications?

Enable 'Show Hidden Files':

Browse to, or paste in the top bar:

/usr/share/applications

You should see:

If they do not exist just copy and paste one of the existing shortcuts you see, and we'll rename it:

docker-desktop.desktop

Open with the text editor, right click on the file and click 'Open With', and select Text Editor.

You need to enter this in to the first shortcut:

[Desktop Entry]
Name=Docker Desktop
Comment=Docker Desktop for Linux
Exec=/opt/docker-desktop/bin/docker-desktop
Icon=/opt/docker-desktop/share/icon.original.png
Type=Application
Keywords=container;docker;
Categories=Development;

And save.

Now we do the same, just copy and paste the new shortcut and call it:

docker-desktop-uri-handler.desktop

Open as with the previous shortcut using the Text Editor and clear the contents of the file and paste in:

[Desktop Entry]
Type=Application
Name=Docker Desktop URI handler
Exec=/opt/docker-desktop/bin/com.docker.url-handler %u
StartupNotify=false
NoDisplay=true
MimeType=x-scheme-handler/docker-desktop;

And save the file. Now you should have the two shortcuts I have shown above..?

All good?

OK. Now open your applications menu, the one that shows all your installed applications and you should now see the icon there for Docker Desktop. Click this and see if Docker Desktop opens for you?

R4v3n · December 19, 2024, 3:27pm

What I did was actually just switching in the /var/run directory in the terminal, and then writing the following commands:

sudo chmod 770 docker.sock
sudo chown :users docker.sock

I guess you could also do:
sudo chmod 770 /var/run/docker.sock
and
sudo chown :users /var/run/docker.sock

After this I was able to connect to docker through Wappler and finally deploy stuff.

Cheese · December 19, 2024, 3:31pm

Never had to do this! If Docker is correctly set-up you should not have to... Only thing you should do is add the group. Not sure why you have to do what you have outlined above but maybe that is a Mint thing...?

R4v3n · December 19, 2024, 5:23pm

Most likely, I guess?
After this it somehow worked though.

I did the group thing and it did not work somehow.
After doing the chmod and chown commands, it worked.

Cheese · December 19, 2024, 5:25pm

Sometimes a quick restart helps especially with anything that sets Operating System Environmental variables. Most important thing is you have everything working.