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

    Unsolved Cloudron build mess up

    Support
    6
    11
    438
    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.
    • scooke
      scooke last edited by

      Hi,
      I had built up the courage to try building and installing the new Omeka S app, but I done messed up.

      Thought his is probably a very obvious step, I don't understand what is meant when I'm asked :

      C:\Users\scooke\cloudron\omeka-s-app>cloudron build
      
      Enter repository (e.g registry/username/org.omekas.cloudronapp): 
      
      https://git.cloudron.io/lenef/omeka-s-app
      

      So I just entered the name of repository from Gitlab. It then failed, and now every other attemp fails. Seems entering the "wrong" registry messed things up. So what is the correct registry? I don't have one of this app other than what I downloaded. I can see from https://docs.cloudron.io/custom-apps/tutorial/#cloudron-cli that

      enter app directory

      $ cd nodejs-app

      build the app

      $ docker build -t username/nodejs-app:1.0.0 .

      push the image. if the push fails, you have to 'docker login' with your username

      $ docker push username/nodejs-app:1.0.0

      is what I'm supposed to do... but what or who is this username?? Is it locally? Is it me? Is it a new registry I make elsewhere? Is it one on my own Gitlab account? Is it the username of whoever's repository I cloned? And now that I've messed it up, how do I reset cloudron build?

      Much thanks for any help or suggestions.

      A life lived in fear is a life half-lived

      1 Reply Last reply Reply Quote 0
      • jimcavoli
        jimcavoli App Dev last edited by

        You can edit/remove the information in $HOME/.cloudron.json that deals with that folder on your machine to correct the repository info or just delete the block to make the CLI re-prompt you on the next run.

        scooke 1 Reply Last reply Reply Quote 1
        • scooke
          scooke @jimcavoli last edited by scooke

          @jimcavoli Great, I found it, it was just named .cloudron.

          What is the proper response for

          Enter repository (e.g registry/username/org.omekas.cloudronapp):
          

          Is this my own repository of the cloned app? Or is it not the repository of the creaters, like so - registry/lenef/omeka-s-app? Is it registry/myusernameoncloudron/omeka-s-app or my local user like registry/melocally/omeka-s-app Or is it yet some other repository that I have to create??

          A life lived in fear is a life half-lived

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

            it's either the public docker registry service, or the new self-hosted one in the app store called docker registry.

            Life of Advanced Technology

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

              @robi I understand the words, but not the meaning!

              Seeing as this is a new repository from these kind people, I don't think they have it listed" (is that the right word?) in the public docker registry service (and I'm not even sure what that is, and what the url would be for it). Same thing for the "new self-hosted one in the app store called docker registry". It is new, I just cloned it, so as far as I know there is no repository in the app store repository ... ok, I followed a few links and found https://git.cloudron.io/cloudron/omeka-s-app, so this is the repository I need, right? The portion I enter is just cloudron/omeka-s-app? or does the "registry" in the Enter repository (e.g registry/username/org.omekas.cloudronapp) refer to https://git.cloudron.io?

              A life lived in fear is a life half-lived

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

                @scooke repository != registry.

                repo = github repo where you found the code

                reg = a docker image repo where the build scripts can place the built image, so that docker can pull it down and install it.

                Life of Advanced Technology

                1 Reply Last reply Reply Quote 0
                • M
                  msbt App Dev @scooke last edited by

                  @scooke the registry refers to a docker registry where you push the image after building it, so it should be either a docker.io registry or you can use the new registry-app from cloudron. I've made a post here that you can follow.

                  1 Reply Last reply Reply Quote 1
                  • K
                    kallados last edited by kallados

                    @scooke I think i get the same problem. Im really not sure about the Name

                    Enter repository (e.g registry/username/org.omekas.cloudronapp)
                    
                    1 Reply Last reply Reply Quote 1
                    • nebulon
                      nebulon Staff last edited by

                      Oh I see the confusion. So indeed what the cli tool asks for here is the docker image registry repository. Not the git repository.
                      I guess we can just remove "repository" here from the cli tool output to avoid that confusion.

                      To clarify an example setting for this for example for the omeka image pushed to the appstore by the Cloudron team: docker.io/cloudron/org.omekas.cloudronapp this has to be set to whatver your docker hub account is, or if another docker registry is used, also the docker.io has to change to your registry domain.

                      K 1 Reply Last reply Reply Quote 0
                      • K
                        kallados @nebulon last edited by kallados

                        @nebulon Sry for maybe stupid Question.. but

                        docker.io/cloudron/org.omekas.cloudronapp
                        

                        "cloudron" should to be replaced with my username right? Or is this pointed to chown cloudron:cloudron? Thanks

                        nebulon 1 Reply Last reply Reply Quote 0
                        • nebulon
                          nebulon Staff @kallados last edited by

                          @kallados indeed it has to be adjusted to your own account name. cloudron here refers to our account at the docker hub. The chown is for the unix user named cloudron on your system. Nothing to do with the docker hub registry service.

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