Closed Ravenwater closed 5 years ago
turned out to be incorrect permissions on my docker-relay.
for anyone running into a similar issue, job management is useful here:
dont specify background($
at the end) when invoking sudo ...
if your auth isn't cached; instead use CTRL+Z
to suspend your job, and bg
to run the most-recently-suspended job in the background.
eg:
(the ^Z
below is when CTRL+Z
is entered, after entering the password for sudo ...
)
ethan@coip:~$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
ethan@coip:~$ ./docker-relay
2020/01/13 15:21:43 socat[281] E bind(5, {AF=1 "/var/run/docker.sock"}, 22): Permission denied
ethan@coip:~$ sudo !!
sudo ./docker-relay
[sudo] password for ethan:
^Z
[1]+ Stopped sudo ./docker-relay
ethan@coip:~$ bg
[1]+ sudo ./docker-relay &
ethan@coip:~$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ethan@coip:~$
Running into the following failure:
From a PS, confirmed that the docker deamon is running
So, how do I debug what is failing?