#Unable to start applications

15 messages · Page 1 of 1 (latest)

cinder seal
#

I just installed Casa OS on my server. I managed to install some applications to it, but I am unable to access them via the browser.

Unable to connect 

Firefox can’t establish a connection to the server at 192.168.0.69:8989

Upon investigating, their docker containers are not running and I can't seem to be able to start them. Am I doing something wrong? I was under the impression this would be taken care of by CasaOS during their installation.

This is the output of docker logs [container ID] for every container:

Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/df005fb87b65/json": dial unix /var/run/docker.sock: connect: permission denied
#

For some reason I am unable to upload a 77 kB screenshot I took of the terminal... So here is the outcome of sudo docker ps:

CONTAINER ID   IMAGE                                              COMMAND   CREATED             STATUS                            PORTS                                       NAMES
113f672eb532   linuxserver/radarr:latest                          "/init"   About an hour ago   Restarting (111) 56 seconds ago                                               Radarr

df005fb87b65   linuxserver/sonarr:latest                          "/init"   About an hour ago   Up 56 minutes                     0.0.0.0:8989->8989/tcp, :::8989->8989/tcp   Sonarr

812128b0a7a2   lscr.io/linuxserver/transmission:version-3.00-r5   "/init"   About an hour ago   Restarting (111) 53 seconds ago                                               Transmission

e6a4b2b085c6   linuxserver/jellyfin:latest                        "/init"   About an hour ago   Restarting (111) 46 seconds ago                                               Jellyfin
plush halo
#

It is happing to me too

cinder seal
real patrolBOT
#

GG @cinder seal, you just advanced to level 2!

obtuse turret
#

Unable to visit CasaOS UI and getting permission denied by docker are two different issues.

For docker, try run the command under root or prepends the command with sudo

#

For CasaOS issue, try curl localhost:8989 on the server and see what gets returned

cinder seal
#

Output of curl: curl: (56) Recv failure: Connection reset by peer

cinder seal
cinder seal
#

I added my user to the docker group and now running docker logs [container ID] outputs this, repeated several times:

s6-svscan: warning: unable to iopause: Operation not permitted
s6-svscan: warning: executing into .s6-svscan/crash
s6-supervise s6-linux-init-shutdownd: fatal: unable to iopause: Operation not permitted
s6-svscan crashed. Killing everything and exiting.
s6-linux-init-shutdownd: fatal: unable to iopause: Operation not permitted
s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted
...
obtuse turret
#

Does every container fail to run?

cinder seal
# obtuse turret Does every container fail to run?

how would I determine that? docker ps output shows they keep restarting, except Sonarr. Running sudo docker start NAME outputs the container name, rather than an error, but the output of docker ps remains the same...

obtuse turret
#

Do docker run hello-world.

If that doesn't run, it's better to forward the issue to the docker community forum.

cinder seal
#

That works: `Hello from Docker!
This message shows that your installation appears to be working correctly.

...`