search

XternA / income-generator

A set & forget, multi-platform, lightweight, self-updating container stack managing passive income applications utilising unused internet bandwidth. With native OS solution for fast deployment in mind with global tool access and multi-proxy support.
Other
73 stars 8 forks source link

Ubuntu 24.04 fresh install. Error on installing apps #33

Closed lalejand closed 1 month ago

lalejand commented 1 month ago

I'm on a computer with ubuntu 24.04 freshly installed. I installed docker via the igm app.

Docker has been installed successfully.
Restart if docker doesn't start properly.
Press Enter to continue...

Then I try to install the income apps via the menu "1. install & run applications" > "1. selective applications" > yes. And I get that:

Installing selective applications...

unable to get image 'proxylite/proxyservice': permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/images/proxylite/proxyservice/json": dial unix /var/run/docker.sock: connect: permission denied

permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Head "http://%2Fvar%2Frun%2Fdocker.sock/_ping": dial unix /var/run/docker.sock: connect: permission denied

permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%3Dcompose%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied

Press Enter to continue...
lalejand commented 1 month ago

Restarted the computer, now it is working. Maybe add this point in instructions.

XternA commented 1 month ago

Yes, the instructions could be better updated to make it more clear.

For future references, this usually is the case when not running with sudo but this would affect those who run it under macOS.

The usual solution is log out the current shell session or a quick restart will allow the new permissions to let docker run and attach to the docker daemon socket.