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. Docker Registry
  3. How do I do this??

How do I do this??

Scheduled Pinned Locked Moved Docker Registry
26 Posts 3 Posters 2.6k 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.
  • scookeS 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)?

    timconsidineT Offline
    timconsidineT Offline
    timconsidine
    App Dev
    wrote on last edited by
    #17

    @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
    0
    • scookeS scooke

      @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!

      timconsidineT Offline
      timconsidineT Offline
      timconsidine
      App Dev
      wrote on last edited by
      #18

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

      1 Reply Last reply
      0
      • scookeS 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)?

        timconsidineT Offline
        timconsidineT Offline
        timconsidine
        App Dev
        wrote on last edited by timconsidine
        #19

        @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
        0
        • scookeS scooke

          @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!

          timconsidineT Offline
          timconsidineT Offline
          timconsidine
          App Dev
          wrote on last edited by
          #20

          @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.

          scookeS 1 Reply Last reply
          1
          • timconsidineT timconsidine

            @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.

            scookeS Offline
            scookeS Offline
            scooke
            wrote on last edited by
            #21

            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

            timconsidineT scookeS 2 Replies Last reply
            0
            • scookeS scooke

              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.

              timconsidineT Offline
              timconsidineT Offline
              timconsidine
              App Dev
              wrote on last edited by timconsidine
              #22

              @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
              0
              • scookeS scooke

                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.

                scookeS Offline
                scookeS Offline
                scooke
                wrote on last edited by
                #23

                @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

                BrutalBirdieB 1 Reply Last reply
                0
                • scookeS scooke

                  @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.

                  BrutalBirdieB Offline
                  BrutalBirdieB Offline
                  BrutalBirdie
                  Partner
                  wrote on last edited by BrutalBirdie
                  #24

                  @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 drink. Cheers!

                  scookeS 1 Reply Last reply
                  0
                  • BrutalBirdieB 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.

                    scookeS Offline
                    scookeS Offline
                    scooke
                    wrote on last edited by
                    #25

                    @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

                    BrutalBirdieB 1 Reply Last reply
                    1
                    • scookeS scooke

                      @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?

                      BrutalBirdieB Offline
                      BrutalBirdieB Offline
                      BrutalBirdie
                      Partner
                      wrote on last edited by BrutalBirdie
                      #26

                      @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 drink. Cheers!

                      1 Reply Last reply
                      2
                      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