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

    How do I do this??

    Docker Registry
    3
    26
    724
    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

      Very unclear topic title, I know. Sorry.

      I'm trying to use some custom apps. I've been able to install at least one, paperless-ng, but I can't find my own notes about how I did it. I have it running on my Cloudron. Now, I'm trying to tackle some others, like @nj's cloudron-keycloak and cloudron-outline. @nj has kindly listed some steps in their github repository, but for someone like me there seem to be steps missing that don't make sense!

      Here is what I think I need to do (using the steps listed plus my own):

      In my Ubuntu VM on Windows, I've clone the respository: git clone https://github.com/njsubedi/cloudron-keycloak.git

      I've then logged into my new Docker Registry on my Cloudron: docker login docker.example.com, and it worked.

      I'm also logged into my Cloudron using the cli on the Ubuntu VM

      I've cd'ed into the clone repository on my Ubuntu VM: cd cloudron-keycloak

      Here is where I falter.

      Do I cloudron build first? Because the instructions say this builds AND publishes the image. But, I haven't set any details yet about publishing anything.

      The next step is to name the image: docker.example.com/me/cloudron-outline (I've reworded it to make more sense for myself), but, does me use the name that I used to login to docker.example.com, my Cloudron Docker Registry, or do I need to make this user or directory?? Or is this not going to be njsubedi by default since I'm working on their image that I cloned? Do I need to clone this on Github to my own Github account before cloning it? But, my Github username is not the same as my docker.example.com Registry user name, so the same question still exists - where does that name me come from?

      Then instructions then say to: Install the app cloudron install -l <auth.yourdomain.tld>, but does this mean, I cd into the cloned directory on my Ubuntu VM, which has had the command cloudron build run on it already, and somehow the cloudron install command knows what docker image to use? So I just run cloudron install -l new.domain.tld and the app will get installed?

      IF SO, then at what point do I push all this my Cloudron's Docker registry??? After the clone? Before the Build? After the Build? After the Install? And, regardless of the answer to that, once I've pushed the image to my own Docker repository... what's the point? It seems like all the work is done on the Ubuntu VM, in the cloned repository. And to then update... I need to pull from @nj's original Github repository, right?? To anyone brave enough to try to help me, thank you.

      I hope my confusion is clear! I'm asking all this before doing anything else other than the initial clone from @nj's Github repository so that I understand it all well and can avoid missing some crucial step.

      A life lived in fear is a life half-lived

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

        @scooke

        I will try to make it very short and understandable 🙂
        Example from Greenlight => https://git.cloudron.io/cloudron/greenlight-app

        git clone ssh://git@git.cloudron.io:6000/cloudron/greenlight-app.git
        cd greenlight-app
        docker build --file Dockerfile --target dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20 .
        docker push dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20
        

        Now if you view your Cloudron Docker Registry you should see your pushed docker image.

        2754f7f1-cc1e-4d39-a71b-0454e8a7c866-grafik.png

        In this screenshot you can see docker images build by cloudron build by the cloudron build service with automated tags, that's why they seem a bit cryptic.

        Now make sure you have setup your docker registry to be used in your Cloudron Server.
        https://my.domain.tld/#/settings => Private Docker Registry

        Now you should be able to install:

        cloudron install --location test --image dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20
        
        App is being installed.
        
         => Queued
         => Registering subdomains
         => Registering location: test.cloudron.dev.......
         => Downloading image ..
         => Creating container
         => Waiting for DNS propagation ...
         => Wait for health check .......................
        
        App is installed.
        

        Cheers 🍻


        Explaining some stuff you asked.

        IF SO, then at what point do I push all this my Cloudron's Docker registry??? After the clone? Before the Build? After the Build? After the Install? And, regardless of the answer to that, once I've pushed the image to my own Docker repository... what's the point? It seems like all the work is done on the Ubuntu VM, in the cloned repository. And to then update... I need to pull from @nj's original Github repository, right?? To anyone brave enough to try to help me, thank you.

        I hope my confusion is clear! I'm asking all this before doing anything else other than the initial clone from @nj's Github repository so that I understand it all well and can avoid missing some crucial step

        You cant push / publish anything if you don't build it first.

        what's the point

        well.. your cloudron server can't just download the docker image from your local computer. 😬

        Like my work? Consider donating a beer 🍻 Cheers!

        scooke 1 Reply Last reply Reply Quote 6
        • scooke
          scooke @BrutalBirdie last edited by scooke

          @BrutalBirdie Thank you, this is really helpful, and I think I've followed it all. I would have left out the --file and --target options in the build step, for example.

          A few questions to help me grasp the concepts...

          Building something to have something to push, pull makes sense. After I've built, and pushed, what happens to the original directory which I built in? Can I delete it?

          If I do delete it, how does that image get updated? Don't I have to re-clone, re-build, re-push, making the first image useless (and every subsequent one after each update).

          If I don't delete it, this means it is an essential directory that I basically will never delete, right? And over time it will get quite large as I pull or clone updates to it?

          For the install, cloudron install --location test --image dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20 can be run anywhere local then, right? It doesn't need to be in that original clone/build directory because I've previously logged in to both my Cloudron and my self-hosted Docker Registry and the --options are used by cloudron install to know where these things are, right?

          As for the final "point" question... must I push the built image somewhere? Can't it/doesn't it just stay in the clone directory (I'm assuming that's where the Docker image is after I've run "build")? If I can just leave it, then the install command would have to locate it, cloudron install --location test --image C://Users/me/cloudron/org.bigbluebutton.greenlight.cloudronapp:1.0.20, something like that, right? So if I can just leave it where it is, this whole Docker Registry thing is just a way to nicely keep built images organized, yes? And I guess for something like Docker Hub, able to share any images.

          A life lived in fear is a life half-lived

          timconsidine 1 Reply Last reply Reply Quote 1
          • timconsidine
            timconsidine App Dev @scooke last edited by

            @scooke said in How do I do this??:

            For the install, cloudron install --location test --image dr.cloudron.dev/org.bigbluebutton.greenlight.cloudronapp:1.0.20 can be run anywhere local then, right? It doesn't need to be in that original clone/build directory because I've previously logged in to both my Cloudron and my self-hosted Docker Registry and the --options are used by cloudron install to know where these things are, right?

            I think it needs to be run from inside the directory where you have CloudronManifest.json.

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

              Welp, I've had the first error, the exact type that has made Docker seem like some super bizarre esoteric only-true-devs-can-use-it, the very first time I've tried to follow @BrutalBirdie's instructions.

              I've run this:

              me@vm:~/cloudron/cloudron-odoo$ docker build --file Dockerfile --target docker.toutdo.com/org.odoo.cloudronapp:1.0.20 .
              [+] Building 0.3s (2/2) FINISHED
               => [internal] load build definition from Dockerfile                                                                                                                                                                                   0.1s
               => => transferring dockerfile: 1.95kB                                                                                                                                                                                                 0.0s
               => [internal] load .dockerignore                                                                                                                                                                                                      0.2s
               => => transferring context: 74B                                                                                                                                                                                                       0.0s
              failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage docker.toutdo.com/org.odoo.cloudronapp:1.0.20 could not be found
              

              Now, all you devs can see clear as day what I did wrong, but it isn't clear to me at all what I did wrong, especially since I followed the instructions. There are always assumptions that seem to exist, assumptions that a non-dev but wanna-be-dev person like me just miss. Clearly the error docker.toutdo.com/org.odoo.cloudronapp:1.0.20 could not be found is that this can't be found... but I looked to me, from the instructions, that it would be built and then "known". So do I just leave out this step? In fact, the very first time I ran this I left off the .

              me@vm:~/cloudron/cloudron-odoo$ docker build --file Dockerfile --target docker.toutdo.com/cloudron-odoo:1
              "docker build" requires exactly 1 argument.
              See 'docker build --help'.
              
              Usage:  docker build [OPTIONS] PATH | URL | -
              
              Build an image from a Dockerfile
              

              I looked at that, then the instructions, telling myself, "look carefully, you left out something", and saw the space period. But this recent error? What the heck? I have to make this directory first? I named it wrong? Let me try without the "target". So now I'm running build without the --target, and 410s (2/3) in, it's still building.

              The message at least tells me that it is looking in/pulling from => [internal] load metadata for docker.io/cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263ea a cloudron source. So I guess it couldn't find one with the name I used for target; but it wasn't clear to me that the name had to be of an existing image. But I also can't find any reference to a ```docker.io/coudron/base:3.2" in this cloudron-odoo repository, so, how in the world did it know to use that?

              Well, this is a Help forum, not a "Teach Programming" forum, so I don't really expect anyone to spend more time trying to help me comprehend this stuff. I'll eventually get it. I hope. I just need to find a source which covers the "assumptions". Thanks again.

              A life lived in fear is a life half-lived

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

                @scooke hope this is not a thick question but exactly which odoo repository are you cloning and building from ? Do you have a link?
                I might give it a try.

                How it knows which base to use ? It is stated in the Dockerfile on the line FROM .....

                Keep persevering. I don't think people mind a blurred line between Help and Tutorial when the questions are good ones (as here).

                BrutalBirdie scooke 3 Replies Last reply Reply Quote 1
                • BrutalBirdie
                  BrutalBirdie Staff @timconsidine last edited by

                  @timconsidine yea the source would be really helpful for debugging.

                  Like my work? Consider donating a beer 🍻 Cheers!

                  1 Reply Last reply Reply Quote 0
                  • BrutalBirdie
                    BrutalBirdie Staff @timconsidine last edited by

                    @timconsidine I think it might be this: https://github.com/njsubedi/cloudron-odoo

                    https://forum.cloudron.io/topic/1256/odoo-distributed-business-apps/25?_=1648412597488

                    Like my work? Consider donating a beer 🍻 Cheers!

                    BrutalBirdie 1 Reply Last reply Reply Quote 1
                    • BrutalBirdie
                      BrutalBirdie Staff @BrutalBirdie last edited by BrutalBirdie

                      git clone git@github.com:njsubedi/cloudron-odoo.git
                      
                      cd cloudron-odoo
                      
                      docker build --file Dockerfile --target dr.cloudron.dev/com.odoo.cloudronapp:0.0.1 .
                      
                      docker push dr.cloudron.dev/com.odoo.cloudronapp:0.0.1
                      
                      cloudron install -l odoo.cloudron.dev --image dr.cloudron.dev/com.odoo.cloudronapp:0.0.1
                      
                      App is being installed.                                                                                                                                                                                                                          => Queued                                                                                                              
                      => Registering subdomains 
                      => Registering location: odoo.cloudron.dev ....... 
                      => Setting up addons
                      => Waiting for DNS propagation ...
                      => Wait for health check ...........                                                                                                                                                                                                           App is installed.
                      
                      

                      and: https://odoo.cloudron.dev

                      🤷 login is admin:admin all working for me.

                      Like my work? Consider donating a beer 🍻 Cheers!

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

                        @timconsidine This is from @nj's github, https://github.com/njsubedi/cloudron-odoo

                        A life lived in fear is a life half-lived

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

                          @BrutalBirdie Interesting... I'm at 3100+ seconds of build time, and it's still going.
                          Is that normal? I ran it without the --target option.

                          A life lived in fear is a life half-lived

                          BrutalBirdie timconsidine 2 Replies Last reply Reply Quote 0
                          • BrutalBirdie
                            BrutalBirdie Staff @scooke last edited by

                            @scooke No that is nor normal.
                            Maybe you can try my steps with copy and paste.

                            Like my work? Consider donating a beer 🍻 Cheers!

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

                              @scooke errrr I think the --target or -t option is MANDATORY
                              You need to tell docker what repo "to build the project into".

                              I just cloned the repo and built without a hitch.

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

                                me@VM:~/cloudron/cloudron-odoo$ docker build --file Dockerfile --target docker.toutdo.com/com.odoo.cloudronapp:0.0.1 .
                                [+] Building 0.3s (2/2) FINISHED
                                 => [internal] load build definition from Dockerfile                                                                                                                                                                                             0.1s
                                 => => transferring dockerfile: 38B                                                                                                                                                                                                              0.0s
                                 => [internal] load .dockerignore                                                                                                                                                                                                                0.1s
                                 => => transferring context: 34B                                                                                                                                                                                                                 0.0s
                                failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage docker.toutdo.com/com.odoo.cloudronapp:0.0.1 could not be found
                                

                                I'm using my Docker Registery which I've installed at docker.toutdo.com, as you can see, but it's that same error about not finding it. I need to use dr.cloudron.dev (which I've been assuming can be changed)?

                                A life lived in fear is a life half-lived

                                timconsidine 3 Replies Last reply Reply Quote 0
                                • timconsidine
                                  timconsidine App Dev @scooke last edited by timconsidine

                                  @scooke so MY terminal output for what you have above is :

                                  TC-MBP-13:cloudron-odoo timconsidine$ docker build -t tcmbp132021/cloudron-odoo:a .
                                  [+] Building 139.3s (11/17)                                                                                                                 [+] Building 139.5s (11/17)                                                                                                                 
                                   => [internal] load build definition from Dockerfile                                                                                   0.1ss
                                   => => transferring dockerfile: 1.95kB                                                                                                 0.1ss
                                   => [internal] load .dockerignore                                                                                                      0.1ss
                                   => => transferring context: 74B                                                                                                       0.0ss
                                   => [internal] load metadata for docker.io/cloudron/base:3.2.0@sha256:ba1d566164a67c266782545ea9809dc611c4152e27686fd14060332dd88263  33.5ss
                                  

                                  I notice your output reports smaller file sizes
                                  My first suspicion would be a network error.
                                  Maybe compounded by you doing this in a local VM ?
                                  I don't know, just taking wild stabs in the dark.
                                  I don't think it is a process issues (commands), smells like network or environment issue to me.

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

                                    @timconsidine Could be. It's late where I am, so I'm hitting the hay. Thanks again, I'll take another stab in the morning!

                                    A life lived in fear is a life half-lived

                                    timconsidine 2 Replies Last reply Reply Quote 0
                                    • timconsidine
                                      timconsidine App Dev @scooke last edited by

                                      @scooke

                                      I'm using my Docker Registery which I've installed at docker.toutdo.com, as you can see, but it's that same error about not finding it. I need to use dr.cloudron.dev (which I've been assuming can be changed)?

                                      Yes, not just 'can', generally you should change it, because the image which is built goes into your repo that you have logged into.

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

                                        @scooke good sleep !
                                        always helps.
                                        You will get this nailed, don't worry.

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

                                          @scooke the following from your message looks strange to me :

                                          [+] Building 0.3s (2/2) FINISHED
                                           => [internal] load build definition from Dockerfile                                                                                                                                                                                             0.1s
                                           => => transferring dockerfile: 38B  
                                          

                                          If I read that correctly, your build process only received a Dockerfile of 38Bytes.
                                          My Dockerfile in the folder of the cloned repo is 1.9KB - NB kilobytes.
                                          38B is hardly enough to specify the base image correctly, let alone the rest of the build instructions.

                                          Maybe do a directory listing and compare to the github listing ?
                                          I withdraw my wild stab 'network' or 'environment' guess.
                                          Instead I make a wild stab 'corrupt github clone' or 'corrupt github download / extraction'.

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

                                            @scooke another thought .....
                                            I went back to your very first message in this topic, and noticed this.

                                            I'm also logged into my Cloudron using the cli on the Ubuntu VM
                                            

                                            I might be reading this wrongly.
                                            But I am NEVER logged in to my Cloudron server when I am building apps for deployment.
                                            Raises the thought in my head : are you building the Odoo app actually on the Cloudron server ??!!
                                            it should be built on local machine, then pushed to docker registry.
                                            Then cloudron install etc should be run locally which does the connection to the Cloudron server.
                                            No need to be on the Cloudron server at all while building.

                                            I am still thinking the issue is mostly a corrupt clone from github.
                                            But worth being clear where the build process is being run.

                                            Anyway, off to bed also.

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

                                              I've resumed attempts, and keep failing on both my Ubuntu VM and Windows Terminal/Powershell:

                                              => => transferring context: 74B                                                                                                                                                                             
                                              failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage dr.cloudron.dev/com.odoo.cloudronapp:0.0.1 could not be found
                                              

                                              This seems like a network problem, but in my Docker I have what I think are all the correct options for integrating Windows Docker with WSL2 Ubuntu.

                                              EDIT: In the last 30 minutes I have:
                                              changed DNS setting in Docker Desktop (and back)
                                              Changed "buildkit" from true to false (in Docker Desktop)
                                              Deleted config.json in my Ubuntu ~/.docker directory
                                              Cleaned and Purged in Desktop
                                              Restarted Docker Desktop

                                              And after each of those, if my Ubuntu WSL was running, I'd restart.

                                              I still keep getting:

                                              Error response from daemon: failed to reach build target dr.cloudron.dev/com.odoo.cloudronapp:0.0.1 in Dockerfile
                                              

                                              @timconsidine No, I'm not logged into my Cloudron box, this is all local.

                                              Anyways, time for work, I'll come back later.

                                              A life lived in fear is a life half-lived

                                              timconsidine scooke 2 Replies Last reply Reply Quote 0
                                              • timconsidine
                                                timconsidine App Dev @scooke last edited by timconsidine

                                                @scooke I did internet search for
                                                failed to solve with frontend dockerfile.v0: failed to create LLB definition: target stage
                                                This produced interesting comment on https://stackoverflow.com/questions/64221861/an-error-failed-to-solve-with-frontend-dockerfile-v0

                                                I had the same issue and all I had to do was to capitalize the Docker configuration filename:
                                                dockerfile > didn't work
                                                Dockerfile > did work
                                                

                                                I see in your example earlier you are using the capitalised version.
                                                But lower down in that thread it refers to "better practice" to use docker build --file ./Dockerfile -t <etc> to ensure it references folder in directory.
                                                Personally I never use --file Dockerfile as it is default.
                                                Also see a comment about WSL and closing terminal.
                                                Also a comment about using DOCKER_BUILDKIT=0 docker build . to track the exact error.
                                                Have a read of thread and see if any of it applies.

                                                I would :

                                                • close terminal and open it again
                                                • cd to directory
                                                • run docker build -t docker.toutdo.com/com.odoo.cloudronapp:0.0.1 n.b. without the --file directive
                                                • see what happens !
                                                1 Reply Last reply Reply Quote 0
                                                • scooke
                                                  scooke @scooke last edited by

                                                  @scooke Couldn't resist another quick effort:

                                                  This time I just followed @nj's instructions in the gihub repositroy and ran simply cloudron build. This prompted me for a docker repository, so I entered mine along with the suggested image name, com.odoo.cloudronapp, and then this was followed by a message stating: Building locally as docker.toutdo.com/com.odoo.cloudronapp:bunchofnumbersandletters and the build commenced. (Oh oh, I left out a username thinking that registry/username/com.odoo.cloudronapp meant registry OR username. Will this be a problem?)

                                                  Thus far it seems like using dr.cloudron.dev was the wrong thing for me to use... but it wasn't clear why!

                                                  Well, this also fails in the end. The error message says it can't find the manifest, App installation error: Installation failed: Unable to pull image docker.toutdo.com/com.odoo.cloudronapp. message: (HTTP code 404) unexpected - manifest for docker.toutdo.com/com.odoo.cloudronapp:latest not found: manifest unknown: manifest unknown statusCode: 404

                                                  The build asked for a docker repository, I gave it mine, it built, and then at the end was automatically pushed to my repository. I can see it in the web GUI.

                                                  I did run the install command without the tag on the image, so I am trying it again with the tag.

                                                  SUCCESS> I guess it needed the tag to install properly.

                                                  OK, I really do need to stop and get to work, just want you all to know I did seemingly successfully clone, build, push and install the Odoo app kindly prepped by @nj... thank you! And thank you to @timconsidine and @BrutalBirdie for helping me out too.

                                                  My last questions are: What do I do with the original clone and build directory? Leave it? Delete it? How will I update the image later if not by doing it all over again??

                                                  Ultimately, it seems to me that the whole point of the Registry is mostly to have a place to keep built Docker images. That's it. I guess that's helpful.

                                                  A life lived in fear is a life half-lived

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

                                                    @scooke said in How do I do this??:

                                                    Thus far it seems like using dr.cloudron.dev was the wrong thing for me to use... but it wasn't clear why!

                                                    Of course dr.cloudron.dev is not wrong for YOU because its MY server 🤣 it was an example, you need to replace dr.cloudron.dev with your docker registry app URL.

                                                    Like my work? Consider donating a beer 🍻 Cheers!

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

                                                      @BrutalBirdie Sure, I see that now. It was one of many assumed pieces of knowledge that I come across while trying to learn this stuff. It's assumed I will realize this is your server. One thing that definitely helped me misunderstand is the cloudron.dev bit... I initially thought that, ok, this is coming from cloudron somehow. Anyway, one hurdle hurdled. One good lesson learned. One detail I will be sure to highlight when I'm helping someone out.

                                                      The second assumption was that I would know that the actual proper target would be asked of me when I ran build, but that wasn't clear at all, in many tuts I've been looking at. Good thing that the cloudron build prompt gave an example too, as otherwise, even with my own Docker Registry installed, I honestly would not have known what to put there exactly. And even then, after it was built, it wasn't clear to me that I needed to include that long alphanumeric tag either on the install command. When it didn't work, and the message didn't make sense, I figured I'd try adding that lengthy bit even though all other examples I've seen have a super short one, like yours! (:0.0.1) or the BBB one (:1.0.20)

                                                      So yes, it's installed! And running.

                                                      But about the original clone and build directory? Do I leave it, taking up space? Do I need it still?

                                                      A life lived in fear is a life half-lived

                                                      BrutalBirdie 1 Reply Last reply Reply Quote 1
                                                      • BrutalBirdie
                                                        BrutalBirdie Staff @scooke last edited by BrutalBirdie

                                                        @scooke

                                                        But about the original clone and build directory? Do I leave it, taking up space? Do I need it still?

                                                        You can delete it.
                                                        Buy if @nj decides to release an update you will have to clone it again, and build the update.

                                                        @BrutalBirdie Sure, I see that now. It was one of many assumed pieces of knowledge that I come across while trying to learn this stuff. It's assumed I will realize this is your server. One thing that definitely helped me misunderstand is the cloudron.dev bit... I initially thought that, ok, this is coming from cloudron somehow. Anyway, one hurdle hurdled. One good lesson learned. One detail I will be sure to highlight when I'm helping someone out.

                                                        Hmmmm I was thinking if I should do the example with placeholders so its more clear.
                                                        Next time placeholders will be used again to highlight the user needs to replace this part themself.

                                                        The second assumption was that I would know that the actual proper target

                                                        There is no 'proper' --target its your own decision how to name the target, I go with the id from the CloudronManifest.json.

                                                        like yours! (:0.0.1) or the BBB one (:1.0.20)

                                                        Because, again its your choice how the image is tagged.

                                                        cloudron build --help
                                                        Usage: cloudron build [options]
                                                        
                                                        Build an app
                                                        
                                                        Options:
                                                        --build-arg <namevalue>                 Build arg passed to docker. Can be used multiple times (default:
                                                        [])
                                                        --build-service-token <token>           Build service token
                                                        -f, --file <dockerfile>                 Name of the Dockerfile
                                                        --set-repository [repository url]       Change the repository
                                                        --set-build-service [buildservice url]  Set build service app URL
                                                        --local                                 Build docker images locally
                                                        --no-cache                              Do not use cache
                                                        --no-push                               Do not push built image to registry
                                                        --raw                                   Raw output build log
                                                        --tag <docker image tag>                Docker image tag. Note that this does not include the repository
                                                        name
                                                        -h, --help                              display help for command
                                                        

                                                        The --tag option lets you chose a tag instead of the cryptic hash.

                                                        Like my work? Consider donating a beer 🍻 Cheers!

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