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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. App Packaging & Development
  3. ECONNREFUSED Error Installing Custom Docker Image

ECONNREFUSED Error Installing Custom Docker Image

Scheduled Pinned Locked Moved App Packaging & Development
9 Posts 4 Posters 1.1k Views 4 Watching
  • 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.
  • M Offline
    M Offline
    ManagedStudios
    wrote on last edited by
    #1

    Hi,
    I want to setup a custom app, Couchbase Server (a nosql database), on my cloudron server.
    I used this Dockerfile:

    FROM couchbase:community-7.2.0
    COPY CloudronManifest.json /CloudronManifest.json
    RUN ln -s /app/data /opt/couchbase/var //persistent data
    EXPOSE 8091-8096 11210-11211
    CMD ["couchbase-server"]  //start server
    

    On my local machine building this docker image and running it is fine. I can reach the web UI on localhost:8091.

    Installing the built image on my cloudron works until it is stuck in the "Starting" process.
    The relevant errors are:

    • Feb 10 13:43:11box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
    • Feb 10 13:43:11box:shell reload (stderr): sudo: unable to resolve host 1001629-690: Name or service not known
    • Feb 10 13:23:00=> Healtheck error: Error: connect ECONNREFUSED 172.18.16.138:8091

    The container actually indicates that the web ui is starting:

    • Feb 10 13:42:41Starting Couchbase Server -- Web UI available at http://<ip>:8091

    Does anybody has an idea how to debug and solve this problem?
    Many thanks!

    girishG 1 Reply Last reply
    1
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      Can you share your CloudronManifest.json also, since the exposed port needs to match the container as well as the healtcheck path may have to be adjusted. All options can be seen in https://docs.cloudron.io/packaging/manifest/

      Further though it looks like this requires exposed port ranges, which Cloudron does not support at the moment. So not sure how much value this will be until we support that.

      M 1 Reply Last reply
      0
      • girishG girish moved this topic from Support on
      • M ManagedStudios

        Hi,
        I want to setup a custom app, Couchbase Server (a nosql database), on my cloudron server.
        I used this Dockerfile:

        FROM couchbase:community-7.2.0
        COPY CloudronManifest.json /CloudronManifest.json
        RUN ln -s /app/data /opt/couchbase/var //persistent data
        EXPOSE 8091-8096 11210-11211
        CMD ["couchbase-server"]  //start server
        

        On my local machine building this docker image and running it is fine. I can reach the web UI on localhost:8091.

        Installing the built image on my cloudron works until it is stuck in the "Starting" process.
        The relevant errors are:

        • Feb 10 13:43:11box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
        • Feb 10 13:43:11box:shell reload (stderr): sudo: unable to resolve host 1001629-690: Name or service not known
        • Feb 10 13:23:00=> Healtheck error: Error: connect ECONNREFUSED 172.18.16.138:8091

        The container actually indicates that the web ui is starting:

        • Feb 10 13:42:41Starting Couchbase Server -- Web UI available at http://<ip>:8091

        Does anybody has an idea how to debug and solve this problem?
        Many thanks!

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #3

        @ManagedStudios said in ECONNREFUSED Error Installing Custom Docker Image:

        COPY CloudronManifest.json /CloudronManifest.json

        this isn't required. Manifest does not need to be inside Docker image.

        M 1 Reply Last reply
        0
        • nebulonN nebulon

          Can you share your CloudronManifest.json also, since the exposed port needs to match the container as well as the healtcheck path may have to be adjusted. All options can be seen in https://docs.cloudron.io/packaging/manifest/

          Further though it looks like this requires exposed port ranges, which Cloudron does not support at the moment. So not sure how much value this will be until we support that.

          M Offline
          M Offline
          ManagedStudios
          wrote on last edited by
          #4

          @nebulon
          Thank you for your response!
          Here's my manifest:
          {
          "id": "de.lfg.cbbuecherteam",
          "title": "couchbase server",
          "author": "Dibbo-Mrinmoy Saha dibbomrinmoy@hotmail.com",
          "description": "database for the buecherteam",
          "version": "1.0.0",
          "healthCheckPath": "/",
          "httpPort": 8091,
          "addons": {
          "localstorage": {}
          },
          "manifestVersion": 2
          }

          Is it possible to support the exposed port ranges with the httpPorts option in the cloudron manifest? If not, do you have an alternative solution to deploy couchbase on the server that is using cloudron?

          girishG 1 Reply Last reply
          0
          • girishG girish

            @ManagedStudios said in ECONNREFUSED Error Installing Custom Docker Image:

            COPY CloudronManifest.json /CloudronManifest.json

            this isn't required. Manifest does not need to be inside Docker image.

            M Offline
            M Offline
            ManagedStudios
            wrote on last edited by
            #5

            @girish
            Yeah, I also realized it eventually 😅

            It would be great if you mention in your tutorial that the manifest file is uploaded automatically when you are in the correct directory.

            1 Reply Last reply
            1
            • M ManagedStudios

              @nebulon
              Thank you for your response!
              Here's my manifest:
              {
              "id": "de.lfg.cbbuecherteam",
              "title": "couchbase server",
              "author": "Dibbo-Mrinmoy Saha dibbomrinmoy@hotmail.com",
              "description": "database for the buecherteam",
              "version": "1.0.0",
              "healthCheckPath": "/",
              "httpPort": 8091,
              "addons": {
              "localstorage": {}
              },
              "manifestVersion": 2
              }

              Is it possible to support the exposed port ranges with the httpPorts option in the cloudron manifest? If not, do you have an alternative solution to deploy couchbase on the server that is using cloudron?

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #6

              @ManagedStudios port range support is being worked on for the next release - https://git.cloudron.io/cloudron/box/-/commit/ec990bd16aa829da145b929322da9e03d4544a56

              M 1 Reply Last reply
              0
              • KubernetesK Offline
                KubernetesK Offline
                Kubernetes
                App Dev
                wrote on last edited by
                #7

                I just want to mention, that using a 3rd party docker image may result in some disadvantages. Usually the Cloudron Base Image is used as base for packaging Apps.

                Most likely you already read it, but just for reference here the Packaging Tutorial

                M 1 Reply Last reply
                0
                • KubernetesK Kubernetes

                  I just want to mention, that using a 3rd party docker image may result in some disadvantages. Usually the Cloudron Base Image is used as base for packaging Apps.

                  Most likely you already read it, but just for reference here the Packaging Tutorial

                  M Offline
                  M Offline
                  ManagedStudios
                  wrote on last edited by
                  #8

                  @Kubernetes
                  Yeah, you're right. I'll use the cloudron base image as soon as port ranges are supported. Thanks :).

                  1 Reply Last reply
                  0
                  • girishG girish

                    @ManagedStudios port range support is being worked on for the next release - https://git.cloudron.io/cloudron/box/-/commit/ec990bd16aa829da145b929322da9e03d4544a56

                    M Offline
                    M Offline
                    ManagedStudios
                    wrote on last edited by
                    #9

                    @girish
                    Very cool, looking forward to it 😁 . When do you think will the release be available? Thank you cloudron team!

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Bookmarks
                    • Search