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 Cloudron Install fails.

    Support
    installation
    4
    10
    152
    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.
    • M
      Mastadamus last edited by girish

      Ubuntu 20.04 LTS fresh build. I am trying to rebuild my cloudron on a new server which I will then restore from backup .

      I keep getting to the spot where it downloads containers then I get the following error message:

      for image in ${images}; do
      docker pull "${image}"
      docker pull "${image%@sha256:}" # this will tag the image for readability
      done
      Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution
      "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolutionfor image in ${images}; do
      docker pull "${image}"
      docker pull "${image%@sha256:
      }" # this will tag the image for readability
      done
      Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution
      "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution

      I can curl "https"//registry-1.docker.io/v2/ from the CLI after the script fails and it returns:

      {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}

      So this makes me think name resolution is good?

      Any help?

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

        once it failed, are you able to resolve registry-1.docker.io ? You can run host registry-1.docker.io via SSH to check this. If this is not working, then check systemctl status unbound which is the local DNS resolver Cloudron is installing.

        M 1 Reply Last reply Reply Quote 0
        • Topic has been marked as a question  nebulon nebulon 
        • M
          Mastadamus @nebulon last edited by

          @nebulon I could resolve it.

          I ran the install script again with --redo and it worked.

          1 Reply Last reply Reply Quote 0
          • Topic has been marked as solved  nebulon nebulon 
          • girish
            girish Staff @Mastadamus last edited by

            @Mastadamus Can you tell me a bit more about your server? It is on a VPS (if so, which one) or is it on a home network?

            The --redo is just a workaround for the moment, I am trying to get to the root cause.

            robi M 2 Replies Last reply Reply Quote 0
            • robi
              robi @girish last edited by

              @girish looks like it's flaky DNS.

              Perhaps you need to have the install script prime all the DNS names referenced in the script?

              Or set a specific DNS server for the duration of the install?

              Or check that all DNS download locations are reachable before continuing?

              Life of Gratitude.
              Life of Advanced Technology

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

                @robi initially, I thought it was flaky DNS too. But I think this is almost like the 5th bug report of the same kind on different networks which makes me think there is something wrong in our install script. I think something about installing unbound+resolvconf makes things go down for a short while (this is why --redo works later).

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

                  @girish ah, maybe it's a sequencing issue, do the unbound install after the downloads?

                  Life of Gratitude.
                  Life of Advanced Technology

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

                    @girish home network. Same home network as the previous cloudron which is still working

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

                      @Mastadamus Once installed, it's all good. this is just a one time install issue.

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

                        @girish yeah it seems to be working great now. Also kudos to your migration process. Restoring from backup was not 2 bad

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