Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved all cloudron apps not responding after reboot, most services down

    Support
    docker
    2
    7
    294
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ianhyzy
      ianhyzy last edited by girish

      I'm not sure what happened but after a reboot most of the services on my cloudron won't come up. Cloudron and Docket start fine but almost everything else has a red dot and all my apps show not responding:
      9a5d31c1-a191-4860-8b3d-e6bdc0a6343e-image.png

      I don't see anything incriminating in the logs but I'm happy to provide SSH access too, I'm baffled.

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @ianhyzy last edited by

        @ianhyzy Could it be you are out of disk space (which is why logs are not showing up) ? If not, can you drop us a mail with ssh access?

        ianhyzy 1 Reply Last reply Reply Quote 0
        • ianhyzy
          ianhyzy @girish last edited by

          @girish Still have a lot of free space left, will send over ssh access

          girish 1 Reply Last reply Reply Quote 0
          • girish
            girish Staff last edited by

            It seems there is some strange docker issue.

            # docker stop ceaf8163e71c
            Error response from daemon: cannot stop container: ceaf8163e71c: Cannot kill container ceaf8163e71c917ad9adf35a5308bed33f35135667a35f8d8fc9f3f3e83f9003: unknown error after kill: runc did not terminate sucessfully: container_linux.go:392: signaling init process caused "permission denied"
            : unknown
            
            1 Reply Last reply Reply Quote 0
            • girish
              girish Staff @ianhyzy last edited by

              @ianhyzy oh it seems you installed docker via snap. See also https://stackoverflow.com/questions/50482315/docker-compose-down-fails-due-to-permission-denied/51734756#51734756

              root         970  0.3  0.5 1418616 96156 ?       Ssl  04:00   0:09 dockerd --group docker --exec-root=/run/snap.docker --data-root=/var/snap/docker/common/var-lib-docker --pidfile=/run/snap.docker/docker.pid --config-file=/var/snap/docker/796/config/daemon.json
              root        2910  0.7  0.2 1207328 47688 ?       Ssl  04:00   0:23 containerd --config /run/snap.docker/containerd/containerd.toml --log-level error
              root        5874  0.0  0.0 108728  7088 ?        Sl   04:00   0:00 containerd-shim -namespace moby -workdir /var/snap/docker/common/var-lib-docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/ceaf8163e71c917ad9adf35a5308bed33f35135667a35f8d8fc9f3f3e83f9003 -address /run/snap.docker/containerd/containerd.sock -containerd-binary /snap/docker/796/bin/containerd -runtime-root /run/snap.docker/runtime-runc
              
              
              
              ianhyzy 1 Reply Last reply Reply Quote 2
              • ianhyzy
                ianhyzy @girish last edited by

                @girish I realized my mistake - I installed docker when it asked on setup. I'm re-installing now and not doing, my mistake. Thanks for the help!

                girish 1 Reply Last reply Reply Quote 0
                • girish
                  girish Staff @ianhyzy last edited by

                  @ianhyzy ah, good to know! basically, the snap version of docker starts with it's own container data which seems totally separate from the normal docker.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Powered by NodeBB